agentsclimarketplace

Engineering

97,255 rows, by stacks then stars

  • Team

    ethanhq/cc-fleet/skills/team Skill

    192★ repo

    Spawn long-lived provider LLM teammates in tmux panes that you message via the native agent-team tools — multi-turn, collaborative, watchable. Use for sustained parallel build/work ("spawn workers", N teammates on N files), or when you need a collaborator you message across turns. NOT a fire-and-forget one-shot or a flat batch of independent prompts — that is /cc-fleet:subagent. NOT a scripted multi-phase run — that is /cc-fleet:workflow.

  • Workflow

    ethanhq/cc-fleet/skills/workflow Skill

    192★ repo

    Orchestrate a MULTI-PHASE, dependent, or resumable run over many provider subagents from a JS script, off the main context (`cc-fleet workflow`). Use for fan-out→barrier→synthesis, per-item pipelines, loop-until-dry, or a run that must survive a kill and `--resume` from its journal. NOT a flat fan-out of independent tasks (that is /cc-fleet:subagent — cheaper, no script); NOT interactive collaboration (that is /cc-fleet:team); NOT trivial single-shot work for the main session.

  • Canvas mcp

    vishalsachdev/canvas-mcp/io.github.vishalsachdev/canvas-mcp MCP server

    191★ repo

    Canvas LMS integration for students and educators with FERPA-compliant analytics and workflows

  • Academic figure prompt pastel

    Azhi-ss/academic-figure-skills/academic-figure-prompt-pastel Skill

    189★ repo

    Pastel airy figure prompts for modern ML papers — ICLR/NeurIPS/ICML soft-panel style with tokens, pills, and rounded type. Use when the user wants pastel academic figures, 现代ML论文配图, or 2024-2025 conference airy aesthetics.

  • Academic figure prompt

    Azhi-ss/academic-figure-skills/academic-figure-prompt Skill

    189★ repo

    JSON figure spec for academic diagrams — exact_text layout control for framework, architecture, module, and comparison figures. Use when the user wants paper figure prompts, 架构图/框架图 specs, or academic-figure JSON (text prompts only as simple fallback).

  • Academic figure workflow

    Azhi-ss/academic-figure-skills/academic-figure-workflow Skill

    189★ repo

    End-to-end academic figure workflow router — from repo or paper to figure prompt via the minimum sibling skills. Use when the user wants a full pipeline, is unsure which academic-figure skill to start with, or says 完整论文配图工作流 / from paper to figure prompt.

  • Academic repo analyzer

    Azhi-ss/academic-figure-skills/academic-repo-analyzer Skill

    189★ repo

    Quick-understanding doc for ML/DL repositories — task type, stack, architecture, and figure-worthy innovations. Use when the user wants repo analysis, 仓库分析, or to understand a codebase before figure planning.

  • Bug fix protocol

    CodeAlive-AI/ai-driven-development/skills/bug-fix-protocol Skill

    188★ repo

    8-step disciplined bug-fix protocol that treats every production bug as two failures — the code defect itself and the testing system that allowed it through. Use when fixing a production bug, investigating a regression, writing a post-mortem, or auditing a missed defect. Triggers on "fix this bug", "production bug", "regression test", "post-mortem", "test gap", "why did the tests miss this".

  • Code that fits in your head

    CodeAlive-AI/ai-driven-development/skills/code-that-fits-in-your-head Skill

    188★ repo

    Software-engineering heuristics based on Mark Seemann's Code That Fits in Your Head (2021), updated for agent-driven development. Use when writing or reviewing code, refactoring accidental complexity or a Big Ball of Mud, controlling technical or architectural debt in generated code, designing APIs and invariants, adding a feature through a walking skeleton and acceptance tests, debugging a defect with reproducible tests or bisection, threat-modelling endpoints and trust boundaries with STRIDE, planning a legacy or Strangler migration with rollback, or setting up a maintainable codebase. Covers decomposition and cyclomatic complexity, cohesion, encapsulation, outside-in TDD, separation of concerns, Git/review discipline, safe evolution, and troubleshooting. Not for language syntax, framework tutorials, production incident response, or performance profiling.

  • Fpf problem solving

    CodeAlive-AI/ai-driven-development/skills/fpf-problem-solving Skill

    188★ repo

    Use First Principles Framework (FPF) to think through hard problems, architect systems, evaluate alternatives, decompose complexity, classify problems or kinds, define quality, apply a pattern, decide under uncertainty, establish causality, reason about time and trends, synthesize architecture, check model fit, recover project/process/case/system/role subjects, trace outside-use dependencies, distinguish relations or occurrences, govern ontic/U-kind admission, synthesize source ontologies, assemble framework publication forms, develop capability for named work, publish multi-view artifacts, refresh SoTA packs, or trace provenance. Also triggers on: FPF, bounded contexts, SoTA packs, assurance calculus, decision theory, causal/temporal reasoning, architecture, modularity, transformation-flow networks, narrative rendering, structural adequacy, cultural evolution, quality gates, lexical discipline, FPF Parts A-I. Not for simple task planning, general philosophy, or Agile unrelated to FPF.

  • Hooks management

    CodeAlive-AI/ai-driven-development/skills/hooks-management Skill

    188★ repo

    Manage hooks and automation for coding agents (Claude Code, Codex CLI, OpenCode). Use when users want to add, list, remove, update, or validate hooks. Triggers on requests like "add a hook", "create a hook that...", "list my hooks", "remove the hook", "validate hooks", or any mention of automating agent behavior with shell commands or plugins.

  • Investigating repository history

    CodeAlive-AI/ai-driven-development/skills/investigating-repository-history Skill

    188★ repo

    Investigate GitHub repository history before risky code changes using git blame/log, GitHub PRs, review comments, squash/rebase/cherry-pick/rename heuristics, and cited evidence. Use when asking why code exists, whether a change is safe, what PR introduced behavior, or before editing API, compatibility, security, concurrency, persistence, migration, or performance-sensitive code.

  • Maintaining macos health

    CodeAlive-AI/ai-driven-development/skills/maintaining-macos-health Skill

    188★ repo

    Hands-on playbook for macOS disk cleanup, dev-machine optimization, and proactive health alerting. Use when the Mac is full or slow, when a process persistently burns CPU, when a kernel panic / watchdog timeout / vm-compressor-space-shortage / Jetsam event happened, when the user asks to free disk space, audit storage, set up disk/memory/CPU alerts, or restore the same monitoring on a new Mac. Built around Mole (`mo` CLI) for safety guards plus a custom LaunchAgent-based alerter for active warnings. Covers Apple Silicon laptops with heavy AI/Docker workloads. Not for general macOS support, hardware diagnostics, networking issues, GUI / window-manager bugs, Time Machine recovery, or broken app installs.

  • Maintaining windows health

    CodeAlive-AI/ai-driven-development/skills/maintaining-windows-health Skill

    188★ repo

    Hands-on playbook for Windows 11 disk cleanup, dev-machine optimization, and proactive health alerting. Use when the PC is full or slow, when a BSOD / Kernel-Power 41 / crash dump / commit-memory pressure happened, when the user asks to free disk space, audit storage, set up disk/memory alerts, or restore the same monitoring on a new PC. Built around native Microsoft-supported tooling (Storage Sense, cleanmgr, DISM, pnputil, vssadmin, wevtutil, powercfg) as the safety floor, a drift-protected HTML cleanup UI, and a Task Scheduler + BurntToast alerter. Covers dev machines with heavy AI/Docker/WSL workloads. Not for general Windows support, hardware diagnostics, GPU/driver troubleshooting, antivirus/malware removal, Windows Update repair, networking, or app-specific performance problems unrelated to disk or memory pressure.

  • Mcp management

    CodeAlive-AI/ai-driven-development/skills/mcp-management Skill

    188★ repo

    Search, install, configure, update, and remove MCP servers across coding agents (Claude Code, Cursor, VS Code, Claude Desktop, Gemini CLI, Codex, Goose, Zed, and more). Supports multi-agent installation via npx add-mcp, the official MCP registry, and direct config editing.

  • Prompt engineering

    CodeAlive-AI/ai-driven-development/skills/prompt-engineering Skill

    188★ repo

    Universal prompt engineering techniques for any LLM. Use when crafting, optimizing, or reviewing prompts for AI models. Triggers on requests like "improve this prompt", "write a system prompt", "optimize my instructions", "help me prompt engineer", "audit this prompt", "review my prompt", or when building agentic systems that need structured prompts.

  • Refactoring csharp

    CodeAlive-AI/ai-driven-development/skills/refactoring-csharp Skill

    188★ repo

    Rename and refactor C# symbols in a .NET solution or multi-solution monorepo with a one-shot Roslyn CLI. Use when the user asks to rename a symbol, preview impact, update references across a solution, or refactor shared projects across several solutions.

  • Repo explorer

    CodeAlive-AI/ai-driven-development/skills/repo-explorer Skill

    188★ repo

    Explore and analyze any repository (local path or remote GitHub/GitLab URL) by delegating to Claude Code CLI (`claude -p`) in non-interactive mode with read-only access. Use when the user asks to explore, analyze, investigate, or research a repository or codebase. Triggers on "explore repo", "analyze repo", "investigate repo", "research codebase", "what does this repo do", "how does this codebase work", "ask about repo", "codebase question", "explore repository", "what API does this project have", "analyze this GitHub repo", "explore https://github.com/...", or any request to understand a repository's structure, API, architecture, or implementation details. Works with both local paths and remote URLs (GitHub, GitLab, Bitbucket).

  • Subagents management

    CodeAlive-AI/ai-driven-development/skills/subagents-management Skill

    188★ repo

    Create, edit, list, move, and delete subagents and skills for coding agents (Claude Code, Codex CLI, OpenCode). Manage AGENTS.md instructions, custom subagent definitions, and skill packages across user and project scopes.

  • Windows qa engineer

    CodeAlive-AI/ai-driven-development/skills/windows-qa-engineer Skill

    188★ repo

    Use when testing Windows 11 desktop apps (WinForms/WPF/UWP) via UFO UIA/Win32 automation MCP. Triggers on "test this Windows app", "QA the app", "run smoke test", "click the button", "fill the form", "check the UI", "Windows automation", "UFO QA", "verify the dialog", or any Windows desktop UI testing task. Not for web/browser testing (use Playwright), mobile testing, or non-Windows platforms.

  • X hook extractor

    sergebulaev/x-skills/.codex-marketplace/x-skills/skills/x-hook-extractor Skill

    184★ repo

    Reverse-engineer the hook from a viral X (Twitter) tweet or thread URL. Identifies which of the 10 canonical 2026 X formulas it uses (one-liner contrarian, data-point, build-in-public, quote-tweet, mini-list, relatable cold-open, listicle-thread, story thread, curiosity-gap, how-I teardown), explains why it worked, and returns a blank template mapped to your topic with its primary goal. Use to learn from a tweet you admire. Not for writing your own (use x-post-writer or x-thread-builder).

  • X hook extractor

    sergebulaev/x-skills/skills/x-hook-extractor Skill

    184★ repo

    Reverse-engineer the hook from a viral X (Twitter) tweet or thread URL. Identifies which of the 10 canonical 2026 X formulas it uses (one-liner contrarian, data-point, build-in-public, quote-tweet, mini-list, relatable cold-open, listicle-thread, story thread, curiosity-gap, how-I teardown), explains why it worked, and returns a blank template mapped to your topic with its primary goal. Use to learn from a tweet you admire. Not for writing your own (use x-post-writer or x-thread-builder).

  • Fixture node skill

    AElfProject/aelf-skills/testdata/skills/fixture-node-skill Skill

    no license184★ repo

    Fixture node skill depending on fixture core.

  • Blue team

    gaasher/Agent-Loop-Skills/loops/blue-team Skill

    183★ repo

    Use when the user has concrete failing cases in code or a guardrail/classifier/filter/prompt/API they own — a red-team failure catalogue OR a CI/CD test-failure report (failing pytest/JUnit tests) — and wants the target patched until those failures are closed without breaking what already works. It points straight at the failed cases (normalize any source with tools/ingest.py), fixes one root-cause class per iteration, and re-checks with tools/verify.py — oracle mode against a red-team oracle, or tests mode against the test suite — keeping a patch only if it closes a class while nothing that passed before regresses, else reverting; loops until every class is closed (dry) or the budget runs out, then opens a pull request with the patch set. The defensive fixer half of a find→fix setup. Not for discovering new failures (that is red-team), and not for editing the oracle, tests, or holdout that define ground truth.

  • Claim verify

    gaasher/Agent-Loop-Skills/loops/claim-verify Skill

    183★ repo

    Use when the user has a results draft or a set of data-backed claims and wants each one adversarially verified against the underlying dataset before publishing — a pre-publication red-team of the findings. Extracts the discrete checkable claims from the draft, reproduces each claim's number against the data, stress-tests it against the threats most likely to kill it (outliers, confounds, Simpson's reversals, tiny subgroups, alternative specifications), and marks it verified, fragile, or refuted; fragile and refuted claims are revised — hedged, scoped, or retracted — until every claim is verified or appropriately qualified. The result is a draft where every surviving claim has been reproduced and survived a stress test. Not for open-ended discovery of new findings over a dataset (that is a data-analysis task), and not for diagnosing a single known anomaly or pipeline failure — this is a gate over an existing draft.

  • Hypothesis gen

    gaasher/Agent-Loop-Skills/loops/hypothesis-gen Skill

    183★ repo

    Use when the user wants to generate and literature-vet a pool of novel, testable research hypotheses for a question or domain. A multi-agent loop: a Generator proposes candidate hypotheses, a LiteratureScout grounds each in real retrieved literature (already known? closest prior work? what gap does it fill?), and a Judge scores them against a fixed rubric and keeps the strong, non-duplicate ones; rounds repeat — mutating toward the open gaps — until fresh rounds stop adding keepers. Not for sharpening or decomposing a research question (no grounding/scoring there), and not for grading an existing written proposal against the literature.

  • Karpathy

    gaasher/Agent-Loop-Skills/loops/karpathy Skill

    183★ repo

    Use when the user wants the LLM to do its own ML research: a fully-autonomous loop that hacks the training code, runs it, and keeps changes that lower a single scalar metric (e.g. val_bpb). One agent proposes one change at a time, runs training in the user's env, keeps it only if the metric improves (advancing a git branch) else reverts, and loops forever until the human interrupts. A faithful adaptation of Karpathy's autoresearch. Not for the analysis-first variant that profiles before editing (that is ml-autoresearch), and not for a budgeted, plateau-stopping refactor.

  • Optimize loop

    gaasher/Agent-Loop-Skills/loops/optimize-loop Skill

    183★ repo

    Use when the user wants to iteratively improve an artifact under a hard correctness bound while minimizing a measured cost — refactoring a code module to cut complexity while its test suite stays green, OR speeding up a SQL query while it returns the same rows. Each iteration applies one focused change, checks a correctness gate that must pass, measures a metric that must drop, and keeps the change only if both hold, else reverts; loops to a plateau or budget. Not for adding features, fixing bugs, or any change that is allowed to alter behaviour or results.

  • Plan loop

    gaasher/Agent-Loop-Skills/loops/plan-loop Skill

    183★ repo

    Use when the user has a coding or engineering prompt and wants it refined into a detailed, executable plan before any code is written — the planning stage of a prompt → plan → execute → debug pipeline. It decomposes the prompt from first principles (objective, end state, environment, building blocks, tools, packages), breaks the work into PR-sized tasks each tied to a component with its files, tests, and dependencies, orders them topologically, splits each into atomic subtasks, then a separate principal-engineer agent critiques the plan for alignment, coverage, sizing, and executability; it revises until the critique passes, emitting a plan.md layout and a structured tasks.json that a junior engineer or a smaller model can execute correctly. Not for executing, scaffolding, or debugging the plan (those are downstream loops), and not for research proposals or experiment plans.

  • Prompt optimize

    gaasher/Agent-Loop-Skills/loops/prompt-optimize Skill

    183★ repo

    Use when the user has a prompt that feeds a system they can already score, and wants that prompt automatically improved to raise the score against their own evaluation command. Makes one targeted quality edit per iteration — clarity, context, specificity, structure, examples, decomposition, guardrails — re-runs the user's eval to measure the metric, and keeps the edit only if the metric improves, else reverts; loops to a target, plateau, or budget. The metric is whatever the user's eval command prints (task accuracy, an LLM-judge score, a pass rate, a tool-call success rate); the loop is metric-agnostic and never edits the eval. Not for writing a prompt from scratch, not for tuning model weights or hyperparameters, and not for one-off manual prompt edits without a score.

  • Swe loop

    gaasher/Agent-Loop-Skills/loops/swe-loop Skill

    183★ repo

    Use when the user has a coding prompt — a feature, bug fix, or refactor — and wants it implemented end to end by a self-checking software loop, not a single pass. It refines the prompt into an executable plan (running the plan-loop internally), then executes the plan task by task: an Engineer subagent implements each PR-sized task editing only source, a separate QA subagent authors the tests that prove the task's acceptance criteria (or grades quality only when tests already cover them), runs the task's tests plus the full accumulated regression suite, and grades the code against a strict conciseness/readability/style-match rubric; the Engineer and QA loop on each task until the tests pass and the quality gate holds, then it commits and opens a pull request for the task — stacked PRs (one per task, each based on the prior) by default, or one combined PR — and moves to the next task. Author and critic have disjoint write scopes (Engineer owns source, QA owns tests) so neither can game the gate. Not for producing a plan without building it (that is plan-loop), and not for tuning a metric on an existing artifact under a fixed correctness bound (that is optimize-loop).

  • Dt dql essentials

    Dynatrace/dynatrace-for-ai/skills/dt-dql-essentials Skill

    181★ repo

    Skills, prompts, and instructions for building AI agents on top of Dynatrace production context

    The same file is in 3 other repositories

  • Dt js runtime

    Dynatrace/dynatrace-for-ai/skills/dt-js-runtime Skill

    181★ repo

    Dynatrace server-side JS runtime — function contract, runtime limits, Web APIs, Node.js modules, fetch with credential vault, and the @dynatrace-sdk/* catalog.

    The same file is in 5 other repositories

  • Dt obs android

    Dynatrace/dynatrace-for-ai/skills/dt-obs-android Skill

    181★ repo

    Instruments an existing Android project (Kotlin or Java) with the Dynatrace Mobile Agent for basic monitoring. Covers zero-to-first-event setup only: Gradle plugin, agent config, and user privacy opt-in. Do not use for advanced Dynatrace configuration beyond initial instrumentation.

  • Dt obs aws

    Dynatrace/dynatrace-for-ai/skills/dt-obs-aws Skill

    181★ repo

    AWS cloud resource monitoring including EC2, RDS, Lambda, ECS/EKS, VPC networking, load balancers, S3, DynamoDB, SQS/SNS, and cost optimization. Use when analyzing AWS infrastructure, resource inventory, security compliance, capacity planning, or cost savings. Trigger: "show EC2 instances", "find RDS databases", "VPC resources", "AWS cost optimization", "Lambda functions", "ECS services", "security groups", "unattached EBS volumes", "AWS load balancer topology", "publicly accessible databases", "AWS dashboards". Do NOT use for explaining existing queries, product documentation questions, generic host CPU/memory metrics (use dt-obs-hosts), application-level tracing (use dt-obs-tracing), or log analysis (use dt-obs-logs).

    The same file is in 6 other repositories

  • Dt obs azure

    Dynatrace/dynatrace-for-ai/skills/dt-obs-azure Skill

    181★ repo

    Azure cloud resources including VMs, VMSS, SQL Database, Storage, AKS, App Service, Functions, VNet networking, load balancers, Event Hubs, Container Apps, and Key Vault. Monitor Azure infrastructure, analyze resource usage, audit security posture, and manage organizational hierarchy across subscriptions and resource groups.

    The same file is in 9 other repositories

  • Dt obs flutter

    Dynatrace/dynatrace-for-ai/skills/dt-obs-flutter Skill

    181★ repo

    Integrate the Dynatrace Flutter Plugin into a Flutter project — dependency setup, config, SDK bootstrap, navigation tracking, and verification. Trigger: "add Dynatrace to Flutter", "Flutter plugin setup", "instrument Flutter app", "integrate Dynatrace Flutter", "mobile observability Flutter", "dynatrace_flutter_plugin". Do NOT use for: querying Flutter RUM data (use dt-obs-frontends), non-Flutter mobile setups, or Dynatrace server-side configuration.

  • Dt obs gcp

    Dynatrace/dynatrace-for-ai/skills/dt-obs-gcp Skill

    181★ repo

    GCP cloud resources including Compute Engine, GKE, Cloud Run, Pub/Sub, VPC networking, DNS, IAM, Secret Manager, and monitoring. Monitor GCP infrastructure, analyze resource usage, audit security posture, and manage organizational hierarchy across projects and folders.

    The same file is in 8 other repositories

  • Dt obs genai

    Dynatrace/dynatrace-for-ai/skills/dt-obs-genai Skill

    181★ repo

    Skills, prompts, and instructions for building AI agents on top of Dynatrace production context

    The same file is in 3 other repositories

  • Dt obs hosts

    Dynatrace/dynatrace-for-ai/skills/dt-obs-hosts Skill

    181★ repo

    Host and process metrics including CPU, memory, disk, network, containers, and process-level telemetry. Use when analyzing infrastructure health, resource utilization, process consumption, or host discovery. Also use when building timeseries queries for host metrics that feed into analytical workflows like anomaly detection, forecasting, or seasonality analysis. Trigger: "show hosts", "CPU usage", "memory utilization", "disk space", "high CPU", "host with most free disk", "top hosts by CPU", "top processes by memory", "Linux hosts in AWS", "what databases are running", "infrastructure costs by cost center", "hosts running EOL Java", "container monitoring", "listening ports", "process resource consumption", "CPU forecast", "memory anomaly", "host seasonality". Do NOT use for explaining existing queries, product documentation questions, Kubernetes pod/workload queries (use dt-obs-kubernetes), AWS cloud resource inventory (use dt-obs-aws), or service-level metrics (use dt-obs-services).

    The same file is in 9 other repositories

  • Dt obs ios sdk

    Dynatrace/dynatrace-for-ai/skills/dt-obs-ios-sdk Skill

    181★ repo

    Set up the Dynatrace iOS SDK (OneAgent) in an iOS project using Swift Package Manager. Automates adding the SPM dependency, creating a Dynatrace.plist configuration file, adding the import statement, adding privacy opt-in code, and building the project. Use this skill when the user wants to integrate, install, add, or set up Dynatrace monitoring in their iOS app. Keywords: Dynatrace, iOS, SDK, OneAgent, setup, install, integrate, SPM, Swift Package Manager, Info.plist, DTXApplicationID, DTXBeaconURL, mobile monitoring, RUM.

  • Dt obs kubernetes

    Dynatrace/dynatrace-for-ai/skills/dt-obs-kubernetes Skill

    181★ repo

    Skills, prompts, and instructions for building AI agents on top of Dynatrace production context

    The same file is in 3 other repositories

  • Dt obs logs

    Dynatrace/dynatrace-for-ai/skills/dt-obs-logs Skill

    181★ repo

    Log querying, filtering, pattern analysis, and error rate calculation. Use when searching application or infrastructure logs, analyzing error patterns, or correlating log data. Trigger: "show error logs", "search logs for keyword", "log error rate", "recent errors", "logs from last hour", "find log entries", "top error messages", "log patterns", "parse JSON logs", "logs by process group", "log trends over time", "log entry counts per minute". Do NOT use for explaining existing queries, product documentation questions, distributed tracing or span analysis (use dt-obs-tracing).

    The same file is in 9 other repositories

  • Dt obs problems

    Dynatrace/dynatrace-for-ai/skills/dt-obs-problems Skill

    181★ repo

    Skills, prompts, and instructions for building AI agents on top of Dynatrace production context

    The same file is in 3 other repositories

  • Dt obs react native

    Dynatrace/dynatrace-for-ai/skills/dt-obs-react-native Skill

    181★ repo

    Integrate the Dynatrace React Native Plugin into a React Native or Expo project — dependency setup, dynatrace.config.js, Babel registration, npx instrumentation, navigation tracking, user privacy options, and verification. Handles both bare React Native and Expo (babel-preset-expo) Babel configuration automatically. Trigger: "add Dynatrace to React Native", "React Native plugin setup", "instrument React Native app", "integrate Dynatrace RN", "mobile observability React Native", "react-native-plugin", "dynatrace react native", "add Dynatrace to Expo", "instrument Expo app", "Dynatrace Expo setup". Do NOT use for: querying RN RUM data (use dt-obs-frontends), non-React Native mobile setups, or Dynatrace server-side configuration.

  • Dt obs services

    Dynatrace/dynatrace-for-ai/skills/dt-obs-services Skill

    181★ repo

    Service performance monitoring with RED metrics (Rate, Errors, Duration) and runtime-specific telemetry for Java, .NET, Node.js, Python, PHP, and Go. Use when analyzing service health, SLA compliance, or runtime issues. Trigger: "service response time", "error rate", "throughput", "SLA compliance", "service mesh overhead", "JVM GC", "Java heap", "Node.js event loop", ".NET CLR", "Python threads", "PHP OPcache", "Go goroutines", "service performance", "p95 latency", "request failures", "database response time by name". Do NOT use for explaining existing queries, product documentation questions, infrastructure metrics (use dt-obs-hosts), log analysis (use dt-obs-logs), or distributed tracing workflows (use dt-obs-tracing).

    The same file is in 9 other repositories

  • Dt obs tracing

    Dynatrace/dynatrace-for-ai/skills/dt-obs-tracing Skill

    181★ repo

    Distributed traces, spans, service dependencies, and request flow analysis. Use when investigating span-level details, failures, performance bottlenecks, or trace correlation. Trigger: "trace analysis", "slow requests", "failed spans", "service dependencies", "distributed trace", "span details", "HTTP status codes in traces", "database query spans", "messaging spans", "gRPC calls", "Lambda cold starts", "trace ID lookup", "exception analysis", "correlate logs and traces", "request attributes". Do NOT use for explaining existing queries, product documentation or configuration questions, service-level RED metrics (use dt-obs-services), log searching (use dt-obs-logs), or problem analysis (use dt-obs-problems).

    The same file is in 9 other repositories

  • Dt sec insights

    Dynatrace/dynatrace-for-ai/skills/dt-sec-insights Skill

    181★ repo

    Skills, prompts, and instructions for building AI agents on top of Dynatrace production context

    The same file is in 3 other repositories

  • Eval design forensics

    wanshuiyin/Anti-Autoresearch/skills/eval-design-forensics Skill

    180★ repo

    Audit whether a paper's EVALUATION DESIGN actually measures what it claims and whether its reporting is complete — the validity layer family D (experiment-forensics) cannot reach. Three patterns: train/test leakage means the reported score may not measure generalization (HP-EVAL-LEAKAGE — adopts the Kapoor & Narayanan 8-type / 3-category leakage taxonomy; the illegitimate-proxy / sampling-bias / pretraining-contamination subtypes hand off as needs_external_check, naming but NEVER running Oren-2023 exchangeability / Shi-2023 Min-K% / Golchin-2023 Time-Travel / BIG-bench canary); a load-bearing LLM judge is conflicted (same model/family as a compared system) or unvalidated (no human-agreement, no bias control) (HP-JUDGE-VALIDITY); a declared condition/metric is dropped or switched to favor the method, or 'best' is chosen with no held-out set (HP-SELECTIVE-REPORTING). Verdict-bearing at L0/L1 from the DESCRIBED protocol — NOT repo-gated like experiment-forensics; L2 only CONFIRMS against split/preprocessing/result files. A fresh cross-model reviewer (gpt-5.6-sol xhigh, read-only, fresh thread per pass) PROPOSES findings, each span-anchored to a ledger claim_id; tools/adjudicate_findings.py DECIDES the verdict. Leakage and under-reporting are usually HONEST methodological errors — every finding describes a discrepancy to CHECK, never an accusation. An LLM generating GROUND-TRUTH labels is HP-FAKE-GT (experiment-forensics) — routed there, not here. Emits eval-design-forensics.findings.json; computes NO verdict. Detect-only. Triggers: "eval design audit", "evaluation validity", "train/test leakage", "data leakage", "is the score measuring generalization", "LLM judge bias", "is the judge validated", "selective reporting", "cherry-picked results", "评估设计审计", "评测有效性", "数据泄漏", "训练测试集泄漏", "裁判模型有没有验证", "选择性报告".

  • Experiment forensics

    wanshuiyin/Anti-Autoresearch/skills/experiment-forensics Skill

    180★ repo

    Audit experiment integrity against the evidence ledger. At L2 (repo + result files present) a fresh cross-model reviewer reads the eval code line-by-line for fake/derived ground truth, score self-normalization, phantom results (a paper number with no backing file/key), dead/uncalled metric code, verified-scope inflation, method-described ≠ method-evaluated drift, synthesized-looking results, placeholder/fake data still wired into a released result, code-output ≠ reported-number mismatch, and missing reproducibility artifacts (an empirical/agent/LLM paper shipping neither code nor the prompts/configs its results need) — every finding span-anchored to a ledger claim_id. At L0/L1 (PDF / source only) the same patterns are surfaced as info-level 'could-not-verify' signals where the ledger gives an anchor (observability_level_required:2) — NEVER a fraud verdict from a PDF. The reviewer PROPOSES findings; tools/adjudicate_findings.py computes the verdict. Detect-only. Triggers: "experiment forensics", "audit the results", "check the eval code", "实验诚实度".

  • Cometchat native expo patterns

    cometchat/cometchat-skills/packages/skills-native/skills/cometchat-native-expo-patterns Skill

    179★ repo

    Integration patterns for Expo managed workflow — app.json config, permissions, gesture handler setup, env vars, Expo Router file-based routing subsection.

  • Cometchat native production

    cometchat/cometchat-skills/packages/skills-native/skills/cometchat-native-production Skill

    179★ repo

    Production-readiness for React Native — server-minted auth tokens, user management CRUD, external-backend recipes (Express / Hono / Firebase Functions / Vercel Serverless). RN has no API routes, so the backend is always external.

  • Cometchat native push

    cometchat/cometchat-skills/packages/skills-native/skills/cometchat-native-push Skill

    179★ repo

    Push notifications for React Native CometChat — APNs + FCM setup, dashboard provider configuration, client registration, token lifecycle, foreground display, background wake, tap-to-deep-link, and the Expo Go / APNs-environment traps that silently break production.

  • Cometchat native testing

    cometchat/cometchat-skills/packages/skills-native/skills/cometchat-native-testing Skill

    179★ repo

    Testing patterns for CometChat React Native — Jest + React Native Testing Library setup, mocking the UI Kit + SDK, testing custom bubbles / headers / composer actions, snapshot pitfalls, E2E with Detox vs Maestro, and CI integration. Covers what to test vs what to skip.

  • Cometchat native troubleshooting

    cometchat/cometchat-skills/packages/skills-native/skills/cometchat-native-troubleshooting Skill

    179★ repo

    Diagnose CometChat React Native UI Kit integration failures — init/login, gesture handler, pod install, iOS privacy manifest, Android Maven, Metro cache, permissions, calls, extensions, v4-to-v5 upgrade. For push-specific symptoms see cometchat-native-push § 12.

  • Cometchat android v5 calls

    cometchat/cometchat-skills/skills/cometchat-android-v5-calls Skill

    179★ repo

    Add CometChat chat & messaging and voice & video calls to any React, Next.js, React Native, Angular, Android, iOS, or Flutter project through your AI coding agent. Works with Claude Code, Cursor, Codex, VS Code Copilot, Windsurf, Cline, Kiro, and 50+ more agents.

  • Cometchat android v5 testing

    cometchat/cometchat-skills/skills/cometchat-android-v5-testing Skill

    179★ repo

    Testing patterns for CometChat Android — JUnit + Mockito setup, mocking the SDK, Espresso UI tests, E2E with Maestro, and CI integration.

  • Cometchat android v5 troubleshooting

    cometchat/cometchat-skills/skills/cometchat-android-v5-troubleshooting Skill

    179★ repo

    Diagnose and fix problems with a CometChat Android integration. Gradle errors, runtime crashes, rendering issues, and version compatibility.

  • Cometchat android v6 builder settings

    cometchat/cometchat-skills/skills/cometchat-android-v6-builder-settings Skill

    179★ repo

    CometChat Android UIKit v6 UIKitSettings configuration — all builder options for SDK init, presence, calling, and host overrides

  • Cometchat android v6 production

    cometchat/cometchat-skills/skills/cometchat-android-v6-production Skill

    179★ repo

    CometChat Android UIKit v6 production readiness — token auth, ProGuard/R8, security checklist, release configuration