agentsclimarketplace

Debug & triage

5,138 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

  • Troubleshooting workflow

    HyunKN/harness-kit/skills/troubleshooting-workflow Skill

    0★ repo

    Use when a concrete failure, regression, or confusing broken state must be debugged systematically and captured in `docs/troubleshooting`. Trigger for failing tests, broken builds, runtime errors, user-reported incidents, or environment-specific failures.

  • Add error handling

    gologo13/agent-skills/skills/add-error-handling Skill

    0★ repo

    Implement comprehensive error handling for the current code to make it robust and resilient ...; keywords: error. Use only on explicit request; skip in routine implementation discussions.

  • Debug issue

    gologo13/agent-skills/skills/debug-issue Skill

    0★ repo

    Help debug the current issue in the code by walking through the debugging process systematic...; keywords: debug, test, error, fix. Use only on explicit request; skip in routine implementation discussions.

  • Docker logs

    gologo13/agent-skills/skills/docker-logs Skill

    0★ repo

    Tail logs from Docker containers to check for errors and monitor application behavior; keywords: docker, error. Use only on explicit request; skip in routine implementation discussions.

  • Uips log parser

    cprima-agents/cpm-agent-skills/skills/uips-log-parser Skill

    no license0★ repo

    Parse and analyse UiPath Studio local execution logs to diagnose automation runs. Use when a developer asks about errors, warnings, duration, or status of a UiPath process run; when troubleshooting a failed, interrupted, or slow automation; when searching for a specific message across multiple runs. Triggers on: UiPath log, execution log, Studio run, robot error, job failed, process crashed, how long did it run, find in log.

  • Golang error handling

    halukerenozlu/bolt-cowork/.agents/skills/golang-error-handling Skill

    0★ repo

    Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code.

  • Systematic debugging

    halukerenozlu/bolt-cowork/.agents/skills/systematic-debugging Skill

    0★ repo

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

    The same file is in 30 other repositories

  • Debugging

    LaProgrammerie/ai-engineering-core/skills/debugging Skill

    0★ repo

    Systematic debugging with drift checks: spec vs code, outdated handoff, reproduce, narrow, minimal fix.

  • Context degradation

    uncfreak1255-code/sawyer-skills-legacy/.claude/skills/context-degradation Skill

    no license0★ repo

    This skill should be used when the user asks to "diagnose context problems", "fix lost-in-middle issues", "debug agent failures", "understand context poisoning", or mentions context degradation, attention patterns, context clash, context confusion, or agent performance degradation. Provides patterns for recognizing and mitigating context failures.

    The same file is in 4 other repositories

  • Systematic debugging

    uncfreak1255-code/sawyer-skills-legacy/.claude/skills/systematic-debugging Skill

    no license0★ repo

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

    The same file is in 30 other repositories

  • Debug

    arendon1/agent-skills/process/debug Skill

    0★ repo

    Disciplined diagnosis loop for hard bugs and performance regressions. Build a tight feedback loop first, reproduce, minimize, hypothesize, instrument, fix, regression-test. Never guess at a fix before root cause is found. Use when the user says "diagnose" or "debug this", or reports something broken, throwing, failing, or slow, or when a build verification fails.

  • Triage

    arendon1/agent-skills/process/triage Skill

    0★ repo

    Move issues through a triage state machine: from raw inbox to labeled, scoped, and ready for planning. Define triage roles/labels, apply them consistently, and surface what is ready to become a plan. Use when managing a backlog of issues or tickets before they become plans, or when the user says "triage", "go through issues", "organize the backlog", "what should I work on", "prioritize issues".

  • Mongodb connection

    Lukk17/agent-standards/.agents/skills/mongodb-connection Skill

    0★ repo

    Optimize MongoDB client connection configuration (pools, timeouts, patterns) for any supported driver language. Use this skill when working/updating/reviewing on functions that instantiate or configure a MongoDB client (eg, when calling `connect()`), configuring connection pools, troubleshooting connection errors (ECONNREFUSED, timeouts, pool exhaustion), optimizing performance issues related to connections. This includes scenarios like building serverless functions with MongoDB, creating API endpoints that use MongoDB, optimizing high-traffic MongoDB applications, creating long-running tasks and concurrency, or debugging connection-related failures.

  • Observability and logging

    Lukk17/agent-standards/.agents/skills/observability-and-logging Skill

    0★ repo

    Structured logging and production observability for services. Logging discipline (one abstraction, levels, correlation IDs, never log secrets), health and metrics and tracing, SLOs, resilient outbound calls (timeouts, retry with backoff, circuit breaker), graceful shutdown, and the canonical startup-readiness log. Use when adding logging, instrumenting a service, or making it operable in production.

  • Crash analytics

    appalize/aso-skills/skills/crash-analytics Skill

    0★ repo

    When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.

    The same file is in 2 other repositories

  • Billing dispute triage assistant

    sisodiabhumca/agent-skills/skills/billing-dispute-triage-assistant Skill

    0★ repo

    Vendor-neutral skill to triage billing disputes and recommend resolution paths with evidence checks.

  • Incident severity calibrator

    sisodiabhumca/agent-skills/skills/incident-severity-calibrator Skill

    0★ repo

    Vendor-neutral skill to calibrate incident severity from impact scope, duration, and customer tier.

  • Kpi anomaly triage

    sisodiabhumca/agent-skills/skills/kpi-anomaly-triage Skill

    0★ repo

    Vendor-neutral skill to analyze KPI time-series data, detect anomalies, and generate a triage summary with likely drivers.

  • Mobile crash triage assistant

    sisodiabhumca/agent-skills/skills/mobile-crash-triage-assistant Skill

    0★ repo

    Vendor-neutral skill to triage mobile crash clusters by release, device, and customer impact.

  • Ops rca hypothesis generator

    sisodiabhumca/agent-skills/skills/ops-rca-hypothesis-generator Skill

    0★ repo

    Generates vendor-neutral root-cause-analysis (RCA) hypotheses from incident symptoms and recent changes, producing a prioritized investigation plan.

  • Privacy dsar triage assistant

    sisodiabhumca/agent-skills/skills/privacy-dsar-triage-assistant Skill

    0★ repo

    Vendor-neutral skill to triage data subject requests and map required systems and timelines.

  • Diagnose

    rynhardt-potgieter/sprint_workflow/plugins/sprint-workflow/skills/diagnose Skill

    0★ repo

    Disciplined bug diagnosis loop — reproduce, minimize, hypothesize, instrument, fix, verify. Use this skill before attempting to fix any non-trivial bug, during Phase 4 fix loops, and inside /sprint-bug-triage. Prevents the "fix the symptom, miss the cause" failure mode.

  • Diagnosing bugs

    MAHDTech/agent-skills/skills/engineering/diagnosing-bugs Skill

    0★ repo

    A disciplined loop for hard bugs and performance regressions. Use when the user says debug or diagnose this, or reports something broken, throwing, failing, flaky, or slow. Insists on building a tight, red-capable feedback loop before hypothesising, then reproduces, minimises, ranks hypotheses, instruments, fixes with a regression test, and runs a post-mortem.

  • Gh triage

    MAHDTech/agent-skills/skills/github/gh-triage Skill

    0★ repo

    Triage a GitHub backlog — move issues and external PRs through a state machine of triage roles (categorise, verify, grill if needed, write agent-ready briefs) using the gh CLI and GitHub labels. Use when triaging your GitHub issues and PRs, deciding what's ready for an agent or a human, or turning a backlog into agent-ready briefs.

  • Tars backlog triage

    MAHDTech/agent-skills/skills/planning/tars-backlog-triage Skill

    0★ repo

    Triage pending backlog issues in `.tars/issues/todo/` to verify their accuracy, check for hallucinations, and add review notes. Reach for this when requested to triage tickets, verify backlog accuracy, or prepare issues for implementation.

  • Debugging and error recovery

    h3y6e/agent-skills/.vendor/skills/debugging-and-error-recovery Skill

    0★ repo

    Guides systematic root-cause debugging. 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.

  • Diagnosing bugs

    h3y6e/agent-skills/.vendor/skills/diagnosing-bugs Skill

    0★ repo

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

  • Gcloud

    h3y6e/agent-skills/.vendor/skills/gcloud Skill

    0★ repo

    Interacts with Google Cloud services using the gcloud CLI safely and efficiently. Covers command validation, data reduction, safety guardrails with a denylist, and workflows for discovery and investigation. You MUST read this skill before invoking any gcloud command. Use when managing cloud resources, querying configurations, or troubleshooting issues via gcloud. Don't use when writing or debugging Google Cloud client library code or raw REST/gRPC API interactions.

  • Systematic debugging

    h3y6e/agent-skills/.vendor/skills/systematic-debugging Skill

    0★ repo

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

  • Triage

    h3y6e/agent-skills/.vendor/skills/triage Skill

    0★ repo

    Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

  • Debug issue

    cristianorj22/arthus-harness/plugins/mcp-code-review-graph/claude/skills/debug-issue Skill

    0★ repo

    Systematically debug issues using graph-powered code navigation (code-review-graph MCP). Companion to the `debugger` agent — graph navigation gives breadth, agent gives depth.

  • Golang error handling

    guynhsichngeodiec/cc-skills-golang/skills/golang-error-handling Skill

    0★ repo

    Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code.

  • Golang observability

    guynhsichngeodiec/cc-skills-golang/skills/golang-observability Skill

    0★ repo

    Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for production monitoring, setting up metrics or alerting, adding OpenTelemetry tracing, correlating logs with traces, migrating legacy loggers (zap/logrus/zerolog) to slog, adding observability to new features, or implementing GDPR/CCPA-compliant tracking with Customer Data Platforms (CDP). Not for temporary deep-dive performance investigation (→ See golang-benchmark and golang-performance skills).

  • Golang performance

    guynhsichngeodiec/cc-skills-golang/skills/golang-performance Skill

    0★ repo

    Golang performance optimization patterns and methodology - if X bottleneck, then apply Y. Covers allocation reduction, CPU efficiency, memory layout, GC tuning, pooling, caching, and hot-path optimization. Use when profiling or benchmarks have identified a bottleneck and you need the right optimization pattern to fix it. Also use when performing performance code review to suggest improvements or benchmarks that could help identify quick performance gains. Not for measurement methodology (see golang-benchmark skill) or debugging workflow (see golang-troubleshooting skill).

  • Golang samber slog

    guynhsichngeodiec/cc-skills-golang/skills/golang-samber-slog Skill

    0★ repo

    Structured logging extensions for Golang using samber/slog-**** packages — multi-handler pipelines (slog-multi), log sampling (slog-sampling), attribute formatting (slog-formatter), HTTP middleware (slog-fiber, slog-gin, slog-chi, slog-echo), and backend routing (slog-datadog, slog-sentry, slog-loki, slog-syslog, slog-logstash, slog-graylog...). Apply when using or adopting slog, or when the codebase already imports any github.com/samber/slog-* package.

  • Golang troubleshooting

    guynhsichngeodiec/cc-skills-golang/skills/golang-troubleshooting Skill

    0★ repo

    Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve debugger, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (see golang-benchmark skill) or applying optimization patterns (see golang-performance skill).

  • Finding triage

    ultimatile/development-skills/skills/finding-triage Skill

    no license0★ repo

    Personalized Development Skills

  • Debug first

    sonhaicoder/haiclaudeskill/skills/debug-first Skill

    0★ repo

    Auto-trigger khi gặp error, bug, exception, traceback, "không chạy", "bị lỗi", "sao lại", "why is", "crash", "undefined", "TypeError", "KeyError", "AttributeError", "ImportError", "ModuleNotFoundError", "FAILED", "AssertionError", "500 Internal Server Error", "CORS", "Cannot read properties", "null reference", "Stack trace", "Traceback (most recent call last)", paste error message, screenshot lỗi. Rule: ĐỌC ERROR MESSAGE TRƯỚC — 80% bugs nằm ngay trong error message. Không đoán, không Google ngay.

  • Cloudwatch logs

    rysk-tanaka/skills/skills/cloudwatch-logs Skill

    0★ repo

    CloudWatchログの取得・検索(Lambda関数のログ解析、エラー調査)

  • Diagnose

    sanjeevafk/agent-skills/skills/mattpocock/diagnose Skill

    0★ repo

    Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

    The same file is in 21 other repositories

  • EvidenceTriage

    mj-deving/pai-skills/skills/Beads/EvidenceTriage Skill

    no license0★ repo

    Turn raw failures into high-signal beads. USE WHEN logs, repro commands, or observed behavior need to become self-contained evidence-first tasks instead of vague TODOs.

  • Debugging

    mj-deving/pai-skills/skills/Troubleshooting/Debugging Skill

    no license0★ repo

    Systematic debugging and error recovery — 6-step triage, Stop-the-Line Rule, non-reproducible bug playbook, competing hypotheses. USE WHEN debugging, fix bug, error recovery, troubleshooting, reproduce bug, find root cause, stack trace, error message, test failing, build broken, not working, investigate bug, diagnose issue, flaky test.

  • Incident

    mj-deving/pai-skills/skills/Troubleshooting/Incident Skill

    no license0★ repo

    Incident management from detection through postmortem. USE WHEN incident, outage, SEV1, SEV2, production down, postmortem, blameless review, incident response, war room, incident update, status page, root cause analysis, 5 whys, incident timeline, on-call.

  • Troubleshooting

    mj-deving/pai-skills/skills/Troubleshooting Skill

    no license0★ repo

    Debugging and incident management — 6-step triage, Stop-the-Line, competing hypotheses for dev-time bugs plus incident detection, response, and blameless postmortems for production issues. USE WHEN debugging, fix bug, error recovery, troubleshooting, reproduce bug, root cause, stack trace, test failing, build broken, incident, outage, SEV1, SEV2, postmortem, blameless review, incident response, 5 whys.

  • Browser

    mj-deving/pai-skills/skills/Utilities/Browser Skill

    no license0★ repo

    Visual verification and browser automation via Playwright. Headless or headed Chrome. USE WHEN browser, screenshot, debug web, verify UI, troubleshoot frontend, automate browser, browse website, review stories, run stories, recipe, web automation.

  • Git bisect forensics

    narenaryan/agent-skills/skills/git/git-bisect-forensics Skill

    0★ repo

    Use when hunting a regression across many commits or tracing the origin of a line/function/string — covers automated bisect, skip, replay, blame -L/-C/-w, and pickaxe search (-S/-G)

  • Go error handling

    narenaryan/agent-skills/skills/go/go-error-handling Skill

    0★ repo

    Use when designing Go error types, choosing error vs panic, or implementing recover — covers structured error types with Unwrap, errors.Is/As, the direct-call rule for recover, re-panic, and panic-as-internal-control-flow for complex parsers

  • Python logging cookbook

    narenaryan/agent-skills/skills/python/python-logging-cookbook Skill

    0★ repo

    Use when configuring Python logging beyond basicConfig — non-blocking handlers for latency-sensitive paths, multi-process log aggregation, propagation control, injecting contextual attributes, dictConfig incremental updates, level routing per handler, or library authors avoiding handler conflicts; covers QueueHandler/QueueListener, SocketHandler, LoggerAdapter vs Filter, contextvars, NullHandler for libraries

  • Diagnose loop

    stevennitesh/programming-agent-skills/skills/.archive/diagnose-loop Skill

    0★ repo

    Use when tests, commands, builds, CI jobs, or workflows fail; behavior is wrong; output or performance regresses; flakes or crashes appear; or an error is not yet understood.

  • Github tracking

    stevennitesh/programming-agent-skills/skills/.archive/github-tracking Skill

    0★ repo

    Use when repo work needs durable GitHub recordkeeping: issue/PRD/slice bodies, claim/status/blocker comments, PR/issue links, readiness fields, or CI/review evidence recorded in GitHub; skip ordinary local work, generic triage, PR publishing, CI debugging, and review-comment resolution when narrower workflows own them.

  • Triage

    stevennitesh/programming-agent-skills/skills/custom/triage Skill

    0★ repo

    Triage raw tracker issues and configured external PR requests through maintainer-approved states and Codex-ready handoffs.

  • Xcratch extension debug

    xcratch/xcratch-skills/skills/xcratch-extension-debug Skill

    no license0★ repo

    Use when debugging an in-development Xcratch extension in VS Code. Trigger phrases: breakpoints not hit, source maps, debug on xcratch.github.io editor, live server HTTPS, extension not loading in editor.

  • Pre release pr triage worktree

    kjuhwa/skills-hub/skills/agents/pre-release-pr-triage-worktree Skill

    0★ repo

    Triage open PRs for a release in a dedicated git worktree, classify each into merge/candidate/supersede/defer, and work the loop end-to-end.

  • Env driven debug flag matrix for jit

    kjuhwa/skills-hub/skills/build-system/env-driven-debug-flag-matrix-for-jit Skill

    0★ repo

    Use a consistently-prefixed family of environment variables (DG_JIT_DEBUG, DG_JIT_DUMP_PTX, DG_JIT_PTXAS_CHECK, ...) to toggle JIT compilation/loading/profiling diagnostics without rebuilding or changing config files.

  • Investigate

    kjuhwa/skills-hub/skills/cli/gstack/investigate Skill

    0★ repo

    Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug directly) when the user reports errors, 500 errors, stack traces, unexpected behavior, "it was working yesterday", or is troubleshooting why something stopped working. (gstack)

  • Gstack openclaw investigate

    kjuhwa/skills-hub/skills/cli/gstack/openclaw/skills/gstack-openclaw-investigate Skill

    0★ repo

    Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to debug, fix a bug, investigate an error, or root cause analysis. Proactively use when user reports errors, stack traces, unexpected behavior, or says something stopped working.

  • Build error triage

    kjuhwa/skills-hub/skills/debug/build-error-triage Skill

    0★ repo

    Systematic triage workflow for build/compilation errors — classify by root cause (missing symbol, signature mismatch, instantiation failure), then isolate the first error before chasing cascades.

  • Debug lockorder detection system

    kjuhwa/skills-hub/skills/debug/debug-lockorder-detection-system Skill

    0★ repo

    Runtime lock-order deadlock detection via a DEBUG_LOCKORDER compile flag that tracks lock acquisition order and reports circular dependencies.

  • Investigate

    kjuhwa/skills-hub/skills/debug/investigate Skill

    0★ repo

    Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug directly) when the user reports errors, 500 errors, stack traces, unexpected behavior, "it was working yesterday", or is troubleshooting why something stopped working. (gstack)

  • Triage issue

    kjuhwa/skills-hub/skills/debug/triage-issue Skill

    0★ repo

    Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.