agentsclimarketplace

Debug & triage

5,150 rows, by stacks then stars

1,113 of these skill files have been read, by 1,020 distinct authors, and what they tell an agent counted. What Debug & triage authors agree on, and what they forbid

  • Debugging

    ironbee-ai/ironbee-devtools-skills/skills/debugging Skill

    3★ repo

    Debug web, Node.js, and Python applications using console inspection, network analysis, and non-blocking code debugging. Use when the user reports bugs, wants to debug JavaScript (browser or backend) or a running Python process, inspect network requests, troubleshoot page/API issues, trace function calls, monitor exceptions, or diagnose Python deadlocks/hung threads.

  • Ironbee node devtools cli

    ironbee-ai/ironbee-devtools-skills/skills/ironbee-node-devtools-cli Skill

    3★ repo

    Skills for IronBee DevTools MCP/CLI

  • Ironbee python devtools cli

    ironbee-ai/ironbee-devtools-skills/skills/ironbee-python-devtools-cli Skill

    3★ repo

    Skills for IronBee DevTools MCP/CLI

  • React debugging

    ironbee-ai/ironbee-devtools-skills/skills/react-debugging Skill

    3★ repo

    Debug React applications by inspecting components, props, and the component tree. Use when the user is debugging React apps, wants to inspect component props/state, find which component renders an element, or understand the React component hierarchy.

  • Debug

    marco-souza/skills/.agents/skills/debug Skill

    no license3★ repo

    Systematically debug issues using a structured REPRO → GATHER → HYPOTHESIZE → TEST → FIX → VERIFY workflow. Use when diagnosing bugs, investigating failures, tracing errors, or troubleshooting unexpected behavior in code. Do NOT use when the issue is already identified and a fix is obvious, for code exploration without a specific problem, or for proactive code review.

  • Web3 triage report

    Olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills/web3-triage-report Skill

    3★ repo

    Bug triage validation system, Immunefi report format, and 20 real paid bounty examples dissected. Use this when validating a finding before submitting, writing an Immunefi report, checking if a bug is actually valid, or studying real examples of paid vulnerabilities.

  • Debugger coordinator

    Ow1onp/hermes-agent-skills/skills/verify/debugger-coordinator Skill

    3★ repo

    Use when debugging complex issues involving multiple modalities (frontend + backend, API + UI, terminal + browser). Coordinates Hermes Agent's built-in debugger, browser, terminal, and vision tools for systematic root-cause analysis.

  • Wp project triage

    ihatesea69/HieuNghi-AI-Skills/wordpress_skills/wp-project-triage Skill

    3★ repo

    Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.

    The same file is in 5 other repositories

  • Systematic debugging

    bhaumikmaan/claude-code-master-skills/skills/systematic-debugging Skill

    3★ repo

    Structured diagnosis of bugs, errors, and stuck processes. Maps symptoms to hypotheses, uses bounded log reading, and produces actionable reports. Use when debugging errors, investigating stuck processes, diagnosing performance issues, or when something isn't working as expected.

  • Github goal issue triage

    schalkneethling/claude-toolkit/skills/github-goal-issue-triage Skill

    3★ repo

    Triage open GitHub issues across one or more repositories against each repository's GOAL.md, create missing p0/p1/p2/p3 priority labels, apply exactly one priority label to each open issue, nominate the next issue to work on per repository, and generate a clean HTML report grouped by project. Use when asked to prioritize, label, rank, audit, or report on GitHub issues based on project goals.

  • Npm trusted publishing github workflow

    schalkneethling/claude-toolkit/skills/npm-trusted-publishing-github-workflow Skill

    3★ repo

    Generate, repair, or debug the GitHub Actions workflow FILE that performs an OIDC trusted publish of a pnpm package — the concrete publish.yml, its test → build → publish job shape, the package tarball artifact handoff, Node-version inference from package.json, pnpm and runtime setup via pnpm/setup, the npm-CLI-version upgrade step, and repository.url/Sigstore provenance matching. Use when the user wants the actual workflow written or fixed, or is debugging a specific CI failure: npm publish E404/E403/422, NODE_AUTH_TOKEN appearing unexpectedly, provenance or id-token errors, pnpm/setup version resolution, or runtime version problems. For the broader publishing SECURITY POSTURE — account 2FA, repository and branch hardening, GitHub environments, changesets versus changelogithub, sole-maintainer risk, or auditing an existing pipeline — use the npm-package-publishing skill instead.

  • Coderabbit triage

    yarlson/yarstack/plugins/yarstack/skills/coderabbit-triage Skill

    3★ repo

    Triage unresolved CodeRabbit feedback on the current GitHub pull request. Use for read-only disposition and, only when separately authorized, scoped remediation and remote thread closure.

  • Diagnosing bugs

    arthjean/skills/skills/diagnosing-bugs Skill

    no license3★ repo

    Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

    The same file is in 17 other repositories

  • Meta debug

    arthjean/skills/skills/meta-debug Skill

    no license3★ repo

    Reproduce-first debugging workflow that diagnoses and fixes errors with targeted local evidence, bounded hypotheses, conditional helpers, two fix attempts maximum, and focused verification. Use when the user provides an error, stack trace, failing command, compiler output, failing test, unexpected behavior, or asks to debug, diagnose, or fix a concrete failure. Do not use for feature implementation, general code review, speculative refactoring, or questions without an observed failure.

  • Agent introspection debugging

    uzysjung/uzys-agent-harness/templates/skills/agent-introspection-debugging Skill

    3★ repo

    Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.

    The same file is in 5 other repositories

  • Debug detective

    JayRHa/AgentSkills/debug-detective Skill

    3★ repo

    Systematically root-causes software bugs using a reproduce → isolate → hypothesize → bisect → verify methodology, replacing guess-and-check debugging with a disciplined, evidence-driven investigation. Use this skill when a user reports a bug, a test is failing intermittently or consistently, behavior differs between environments, a regression appeared after a change, something "used to work" and now doesn't, an error/stack trace needs root-causing, or when asked to "debug", "find the root cause", "figure out why X happens", or "track down" a defect. Triggers include crashes, wrong output, flaky tests, hangs/deadlocks, memory leaks, performance regressions, heisenbugs, and works-on-my-machine problems.

  • Error handling patterns

    JayRHa/AgentSkills/error-handling-patterns Skill

    3★ repo

    Designs robust, production-grade error handling — choosing between result types and exceptions, implementing retries with exponential backoff and jitter, applying timeouts and deadlines, adding circuit breakers, and building graceful degradation and fallbacks. Use this skill when writing or reviewing code that calls networks/databases/external APIs, when asked to "make this resilient", "add retry logic", "handle failures", "add timeouts", "handle errors properly", "make this fault tolerant", "add a circuit breaker", "stop swallowing exceptions", or when classifying errors as transient vs permanent and deciding what to retry, fail fast, or degrade.

  • Incident postmortem

    JayRHa/AgentSkills/incident-postmortem Skill

    3★ repo

    Facilitates blameless incident postmortems by reconstructing a precise timeline, identifying root cause and contributing factors, and producing tracked, owned action items. Use this skill when an incident, outage, SEV, or production failure has been resolved and someone needs to "write the postmortem", "do a retro on the outage", "run a blameless RCA", "fill out the incident report", "find the root cause", or "track follow-up action items" after a service disruption.

  • Observability setup

    JayRHa/AgentSkills/observability-setup Skill

    3★ repo

    Instruments applications with structured logging, metrics, and distributed traces, then derives SLIs, SLOs, error budgets, and alerts that page only on user-facing pain. Use this skill when the user asks to "add observability", "instrument my app", "set up OpenTelemetry/OTel", "add structured logging", "expose Prometheus metrics", "add tracing", "define SLOs/SLIs", "set up alerting", "reduce alert noise", "build a Grafana dashboard", or wants the three pillars (logs/metrics/traces) wired into a service.

  • Vulnerability triage

    JayRHa/AgentSkills/vulnerability-triage Skill

    3★ repo

    Triages and prioritizes security vulnerabilities (CVEs) by combining CVSS base/temporal scores, real-world exploitability (EPSS, KEV, public PoCs), environmental exposure (internet-facing, network reachability, authentication), and business impact (data sensitivity, asset criticality) into a defensible, ranked remediation plan with SLAs. Use this skill when asked to triage CVEs, prioritize a vulnerability scan, assess whether a CVE is exploitable or reachable in a given environment, decide patch urgency, set remediation SLAs, write a vulnerability risk assessment, deduplicate scanner findings, or answer "how bad is CVE-XXXX-YYYYY for us?" / "should we drop everything to patch this?".

  • Check logs

    hcaiano/skills/skills/check-logs Skill

    3★ repo

    Henrique Caiano's custom agent skills (Claude, Codex, herdr). Install with: npx skills@latest add hcaiano/skills

  • Debug mode

    hcaiano/skills/skills/debug-mode Skill

    3★ repo

    Evidence debugging for unresolved bugs. Use when the user says 'diagnose' or 'debug this', or when a bug is flaky, environment-specific, production-only, or its root cause survived a normal reproduction/inspection. Build a feedback loop, collect runtime evidence, and fix only after evidence identifies the cause. Do not use for a compiler/type/lint/test error whose cause is in the output, a review finding that already names cause and fix, an already-proven root cause, or from inside an active debug-mode run.

  • Cosec troubleshoot

    Ahoo-Wang/skills/plugins/ahoo-cosec-skills/skills/cosec-troubleshoot Skill

    3★ repo

    Use when diagnosing CoSec authentication or authorization failures such as unexpected 401/403 responses, denied requests that should be allowed, policies not loading, JWT token rejection, matcher mismatches, or unclear access decisions.

    The same file is in 1 other repository

  • Wow debugging

    Ahoo-Wang/skills/plugins/ahoo-wow-skills/skills/wow-debugging Skill

    3★ repo

    Use when Wow commands, events, sourcing, sagas, projections, wait plans, Query DSL, retry policies, starter configuration, or tests fail, hang, skip handlers, produce unexpected state, or behave inconsistently

  • Cosec troubleshoot

    Ahoo-Wang/skills/sources/CoSec/skills/cosec-troubleshoot Skill

    3★ repo

    Use when diagnosing CoSec authentication or authorization failures such as unexpected 401/403 responses, denied requests that should be allowed, policies not loading, JWT token rejection, matcher mismatches, or unclear access decisions.

    The same file is in 1 other repository

  • Wow debugging

    Ahoo-Wang/skills/sources/Wow/skills/wow-debugging Skill

    3★ repo

    Use when Wow commands, events, sourcing, sagas, projections, wait plans, Query DSL, retry policies, starter configuration, or tests fail, hang, skip handlers, produce unexpected state, or behave inconsistently

  • Quarkus debug

    kinhluan/rules-quarkus-skills/.agent-skills/quarkus-debug Skill

    3★ repo

    Expert skill for deep debugging of Quarkus applications, covering Dev Mode, Reactive patterns (Mutiny), Native Image (AOT) issues, and Build-time (Augmentation) troubleshooting.

  • Debug and test

    hec-ovi/agentickit/.pilot/skills/debug-and-test Skill

    3★ repo

    Run the workspace locally, the test suite, and the todo example. Covers the pnpm workspace layout, the `agentickit` build pipeline (tsup), the Vitest config, and the most common "why is this not working" symptoms. Use when something's broken or a contributor is trying to reproduce a bug.

  • Triage

    nikhilw/structured-agentic-workflow/skills/triage Skill

    3★ repo

    Recommend what to work on next by reading the backlog (bugs.md, features.md, plans/) and considering what is already loaded in the current conversation context. Minimizes context thrash — prefers tasks aligned with current context. Recommends bugs when context is low, features when resources are plentiful.

  • Forge

    claudialnathan/agent-kitchen/skills/forge Skill

    no license3★ repo

    Designs coding-agent harness artifacts. One triage ladder picks the right surface (skill, hook, path-scoped rule, CLAUDE.md or AGENTS.md entry, workflow script, subagent, MCP); the stance holds the bar every artifact must clear (a gradeable objective, a gap between the model's default and what the owner wants, and a nameable attention shift; the gap is a new idea or source worth operationalizing, a miscommunication to prevent, or an observed failure); per-surface mechanics live in references. Use for creating, reviewing, or refactoring any of these, for distilling articles or docs into one, for skills that under- or over-trigger, hooks that don't fire or fire too often, bloated CLAUDE.mds, and for deciding which surface a behavior belongs on. Triggers on any work on a skill, hook, rule, CLAUDE.md, AGENTS.md, or workflow orchestration script, including debugging triggering or firing semantics and packaging a /command or plugin.

  • Admin sharing troubleshooting

    PranavNagrecha/Salesforce-Intelligence/.claude/skills/admin-sharing-troubleshooting Skill

    3★ repo

    Salesforce Org Intelligence for AI agents - a read-only, offline, source-available MCP server and CLI answering metadata, dependency, permission, Apex and Flow questions grounded in real retrieved org metadata.

  • Systematic debugging

    rolandbrecht/agent-skills/systematic-debugging Skill

    3★ repo

    Trigger this AUTOMATICALLY anytime you encounter a stack trace, test failure, production bug, or unexpected behavior. Do NOT guess the fix or propose code changes before explicitly triggering this skill. This skill mandates a strict data-gathering and hypothesis phase before you are permitted to edit ANY source code.

  • Debug mining engine

    EvezArt/evez-skills/skills/debug-mining-engine Skill

    no license3★ repo

    32 AI agent skills for credit, finance, data intelligence, and document generation — by Steven Crawford-Maggard (EVEZ)

    The same file is in 2 other repositories

  • Systematic debugging

    EvezArt/evez-skills/skills/systematic-debugging Skill

    no license3★ repo

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

    The same file is in 2 other repositories

  • Web debug

    sentimony/skills/skills/web-debug Skill

    no license3★ repo

    You MUST use this when interacting with or testing local web applications with Playwright — verifying frontend functionality, debugging UI behavior, capturing browser screenshots, or viewing browser console logs.

  • Diagnose loop

    tmusser/ai-engineering-skills/skills/diagnose-loop Skill

    3★ repo

    Debug failures systematically.

  • Android debugging

    adrigm06/Android-Engineering-Skill/skills/android-debugging Skill

    3★ repo

    Android debugging skill for root-cause analysis using hypothesis-driven workflows, reproduction plans, instrumentation, and narrowing strategies. Use when bugs are intermittent, hard to reproduce, or cross-layer.

  • Greybeard

    ManojLingala/greybeard/plugins/claude-code/skills/greybeard Skill

    3★ repo

    Makes your AI agent defensive about the backend failure modes that page you at 3am. Before writing server-side code, the agent stops at a ladder of hard-won rules — money as integer minor-units, idempotent mutations, timeouts and backoff on every external call, explicit transaction boundaries, no N+1 queries, structured logging with no secrets. Paranoid about the right things, never about the wrong ones. Examples lean .NET/C# and EF Core but the rules are language-agnostic.

  • Commit triage

    Axect/skills/commit-triage Skill

    3★ repo

    Classify uncommitted changes into commit-ready, failure-archive, and ambiguous buckets, then produce clean grouped commits with no co-author attribution. Use when the user asks to commit, tidy up `git status`, prepare a PR, archive failed experiments to a `failure/` folder, separate research artifacts from code before a commit, or clean up a noisy working tree at the end of a session.

  • Tailscale docker debug

    rshade/agent-skills/skills/tailscale-docker-debug Skill

    3★ repo

    Diagnose Tailscale connectivity and DNS failures inside Docker containers. Detects userspace vs kernel mode, DNS resolver conflicts, TUN interface issues, and multi-tailnet mismatches. Use when Tailscale peers connect by IP but MagicDNS names fail, or when containers fall back to userspace networking unexpectedly. Also use when a customer deploys Tailscale in Docker or Podman and reports DNS not working, or when migrating from docker run to docker compose breaks TUN functionality.

  • Tailscale subnet router debug

    rshade/agent-skills/skills/tailscale-subnet-router-debug Skill

    3★ repo

    Diagnose Tailscale subnet router connectivity failures. Traces the full route lifecycle: advertisement, approval, client acceptance, policy routing (table 52), and IP forwarding. Use when clients can reach Tailscale peers by IP but not devices on advertised subnets, or when subnet routes appear approved but traffic doesn't flow. Also use when Docker containers fail to advertise routes, when `ip route` shows no subnet route (it's in table 52), or when traffic flows one way but responses don't return.

  • Gate discipline diagnose

    jposluns/grc_library/dev-security/claude-rules/skills/gate-discipline-diagnose Skill

    2★ repo

    Diagnoses a failing CI gate, lint, or audit and fixes the artefact rather than weakening the gate. Use when a gate fails. Use when tempted to bypass a check with --no-verify, blanket suppression, severity-threshold lowering, or exemption-list addition. Use when a pre-commit hook blocks a commit. Use when a required status check on a PR shows red.

  • Query loki project logs

    Sube-py/awesome-skills/skills/query-loki-project-logs Skill

    no license2★ repo

    Query Grafana Loki logs that are organized by labels such as `project_name` or `project`, `env`, and `filename`, where `filename` distinguishes `nginx`, `web`, `worker`, `stdout`, and `stderr` streams. Use when Codex needs to inspect logs with `logcli`, discover available projects or environments, list a project's log files, narrow to a specific component such as web or worker, or check a recent time window for errors in test or local environments.

  • Debugging and error recovery

    LLl0k0laD/agent-skills/skills/debugging-and-error-recovery Skill

    2★ repo

    Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

  • Analytics

    launch52-ai/flutter-template/.claude/skills/analytics Skill

    2★ repo

    Analytics and crash reporting with Firebase Analytics, Crashlytics, Sentry, or PostHog. Event tracking, user properties, screen views, crash reports, error logging. Plug-and-play provider architecture. Use when implementing analytics, crash reporting, or switching providers.

  • Fix the root cause

    Fergius-Engineering/instincts/skills/fix-the-root-cause Skill

    2★ repo

    Use when fixing any bug, especially one that surfaces far from where the bad state was created.

  • Logging for remote diagnosis

    Fergius-Engineering/instincts/skills/logging-for-remote-diagnosis Skill

    2★ repo

    Use when building any mechanic that could fail on a machine out of reach - a shipped product, a CLI a user runs, a server.

  • Triage report

    RockyHong/super-bootstrap/plugins/super-bootstrap/skills/triage-report Skill

    2★ repo

    Drain the `.review/` report queue. Resolves un-triaged scan/audit reports (producer-agnostic — check-docs-consistency and any other scanner), dispatches the `triage-report` subagent (Sonnet) one report at a time for per-finding dispositions (promote / patch / dup / needs-investigation / dismiss), then the gateway absorbs: promotes batch through /super-bootstrap:log, doc-mechanical patches land per CLAUDE.md § Dispatch, investigations route to /super-bootstrap:triage, report deleted at close-out once every finding holds a terminal verdict. Use when a report lands in `.review/` or the user asks to process review findings. Does NOT fix findings.

  • Triage

    RockyHong/super-bootstrap/plugins/super-bootstrap/skills/triage Skill

    2★ repo

    Read-only verdict phase for a backlog card. `/super-bootstrap:triage {ID}` dispatches the `triage` subagent (Opus) to trace the card's root cause cold and emit a verdict artifact — auto-fix → docs/work/triage/{ID}-scope.md (Fix-shape / Probe-deps / Execution tags) or surface → {ID}-notes.md (decision for the user). No code changes — the fix is a separate phase. Use at raw-card pickup (todo board `Triage:` rows) or when the user asks to triage/investigate a BUG/DEBT/GAP item.

  • Debug playbook

    atuljha23/holocron/skills/debug-playbook Skill

    2★ repo

    Hypothesis-driven debugging — reproduce, hypothesize, probe, locate, fix, guard. Use when something is broken and you don't yet know why.

  • Ozor prompt optimizer

    renalpelvisdeinocheirus70/ozor-skills/skills/ozor-prompt-optimizer Skill

    2★ repo

    Analyze and improve existing Ozor.ai video prompts for better output quality. Use this skill whenever the user has an Ozor prompt that produced mediocre results, wants to improve a video prompt, needs help debugging why a video didn't turn out well, or wants expert feedback on their prompt before running it. Trigger on phrases like 'improve this prompt', 'optimize my Ozor prompt', 'why did my video look bad', 'fix this prompt', 'make this prompt better', 'review my Ozor prompt', 'the video didn't turn out right', 'prompt feedback', 'better results from Ozor', or any request to refine, debug, or enhance an existing Ozor video prompt.

    The same file is in 1 other repository

  • Debug

    2389-research/firebase-development/skills/debug Skill

    2★ repo

    This skill should be used when troubleshooting Firebase emulator issues, rules violations, function errors, auth problems, or deployment failures. Triggers on "error", "not working", "debug", "troubleshoot", "failing", "broken", "permission denied", "emulator issue".

  • Ss troubleshooting workflow

    lbk-open/super-spec/skills/ss-troubleshooting-workflow Skill

    2★ repo

    End-to-end defect fix — takes an issue link, alert ID, or problem description and orchestrates root-cause investigation, human confirmation, branching, a fix plan, multi-agent coding with built-in review, and PR/commit delivery. Use only when the user explicitly asks for the full diagnose-to-delivery pipeline, not for diagnosis alone.

  • Devrites debug recovery

    ViktorsBaikers/DevRites/pack/.claude/skills/devrites-debug-recovery Skill

    no license2★ repo

    Debug application failures: tests, builds, CI, runtime exceptions, browser errors, app 500s. Reproduce, rank hypotheses, fix root cause, regression-test. Use when "debug", "build is red", "tests fail", or the app is broken. Not for DevRites install health.

  • Devrites debug recovery

    ViktorsBaikers/DevRites/pack/generated/claude/skills/devrites-debug-recovery Skill

    no license2★ repo

    Debug application failures: tests, builds, CI, runtime exceptions, browser errors, app 500s. Reproduce, rank hypotheses, fix root cause, regression-test. Use when "debug", "build is red", "tests fail", or the app is broken. Not for DevRites install health.

  • Devrites debug recovery

    ViktorsBaikers/DevRites/pack/generated/codex/skills/devrites-debug-recovery Skill

    no license2★ repo

    Internal DevRites skill; DevRites agents invoke it explicitly, not by prompt match.

  • Debugger

    cubha/claude-workflow-plugins/plugins/debugger/skills/debugger Skill

    2★ repo

    버그 원인을 시스템 로그 기반으로 특정하고 수정·검증·정리까지 완료하는 디버깅 워크플로우 스킬. 트리거: '디버깅해줘', '버그 원인 찾아줘', '어디서 오류나는지', '로그 삽입해줘', 에러 메시지/스택 트레이스 붙여넣기, '--pw'/'--pw --headless'/'--pw --record' 플래그. 지원 언어: JS/TS, Python, Java, Kotlin. 안티-트리거: 단순 코드 리뷰, 신규 기능 구현, 원인이 이미 특정된 경우(수정만 진행), 성능 최적화, 기능 동작 검증/시나리오 PASS-FAIL 판정.

    The same file is in 2 other repositories

  • Linmas incident triage lead

    TanKimGwan/linmas/plugins/linmas/skills/linmas-incident-triage-lead Skill

    no license2★ repo

    Incident triage skill for security-event classification, containment planning, evidence preservation, and response coordination.

  • Linmas incident triage lead

    TanKimGwan/linmas/skills/linmas-incident-triage-lead Skill

    no license2★ repo

    Incident triage skill for security-event classification, containment planning, evidence preservation, and response coordination.

  • Debugging

    Noorkhalel/saas-ai-skills/skills/debugging Skill

    2★ repo

    Investigate and safely fix an active, observable software failure, error, regression, or unexpected behavior using reproduction and evidence. Use for the proximate technical cause and remediation. Do not use for a systemic incident postmortem or general performance tuning without a failure.