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

  • Binary search debugging

    Amey-Thakur/AI-SKILLS/skills/debugging/binary-search-debugging Skill

    14★ repo

    Halve the search space repeatedly across code, data, time, and configuration until a single change isolates the failure. Use when the fault could live anywhere across a large surface and reading it all in order is too slow.

  • Debugger fluency

    Amey-Thakur/AI-SKILLS/skills/debugging/debugger-fluency Skill

    14★ repo

    Drive a real debugger with breakpoints, watch expressions, and conditional stops to read live program state at the moment of failure. Use when a bug needs you to see the call stack and variables as it breaks, not reconstruct them afterward.

  • Debugging

    Amey-Thakur/AI-SKILLS/skills/debugging/debugging Skill

    14★ repo

    Find the root cause of a bug with a hypothesis-driven loop instead of guess-and-patch. Use when something fails, crashes, or behaves wrongly and the cause is not yet known.

  • Git bisect

    Amey-Thakur/AI-SKILLS/skills/debugging/git-bisect Skill

    14★ repo

    Find the exact commit that introduced a regression by driving git bisect with an automated pass/fail script. Use when a behavior worked in an older build and you need the first bad commit out of hundreds, not a guess.

  • Log analysis

    Amey-Thakur/AI-SKILLS/skills/debugging/log-analysis Skill

    14★ repo

    Mine logs for the cause of a failure by pivoting on correlation ids, clamping the time window, and querying structured fields instead of scrolling. Use when production broke and the logs are the only record of what the system actually did.

  • Network debugging

    Amey-Thakur/AI-SKILLS/skills/debugging/network-debugging Skill

    14★ repo

    Diagnose failing or slow network calls by inspecting the actual bytes on the wire with curl, tcpdump, and TLS handshake analysis. Use when a request fails, hangs, or returns the wrong thing and you cannot tell whether the client, the network, or the server is at fault.

  • Postmortem debugging

    Amey-Thakur/AI-SKILLS/skills/debugging/postmortem-debugging Skill

    14★ repo

    Reconstruct what happened from the artifacts a dead incident left behind: logs, metrics, dumps, and a timeline, when there is no live system left to poke. Use when the outage is over, the process is gone, and all you have is what was written down while it burned.

  • Print debugging

    Amey-Thakur/AI-SKILLS/skills/debugging/print-debugging Skill

    14★ repo

    Place labeled, greppable print statements at decision points to trace the real execution, then remove them cleanly. Use when a debugger is unavailable or awkward and you need to watch values flow through the actual run.

  • Production debugging

    Amey-Thakur/AI-SKILLS/skills/debugging/production-debugging Skill

    14★ repo

    Debug a live system without making the incident worse by staying read-only first, gating changes behind flags, and testing on mirrored traffic. Use when a bug only manifests in production and you must investigate against real users and real data.

  • Scientific debugging

    Amey-Thakur/AI-SKILLS/skills/debugging/scientific-debugging Skill

    14★ repo

    Debug by turning a belief about the code into a falsifiable hypothesis, predicting an observable, and running the one probe that can refute it. Use when a bug resists guesswork and shotgun edits are making the code murkier instead of the cause clearer.

  • Stack trace reading

    Amey-Thakur/AI-SKILLS/skills/debugging/stack-trace-reading Skill

    14★ repo

    Read a stack trace to find the cause frame instead of stopping at the symptom on top. Use when an exception, panic, or error dump lands and you need to locate the line that is actually wrong.

  • Structured logging

    Amey-Thakur/AI-SKILLS/skills/debugging/structured-logging Skill

    14★ repo

    Emit machine-readable key-value events instead of prose sentences, with a stable schema and controlled field cardinality. Use when logs need to be queried and aggregated, not just read one line at a time by a person.

  • Time travel debugging

    Amey-Thakur/AI-SKILLS/skills/debugging/time-travel-debugging Skill

    14★ repo

    Record an execution once and replay it deterministically so you can step backward to the moment a value went wrong. Use when a bug is hard to reproduce or the failure surfaces long after its cause, and rerunning changes the outcome.

  • Embedded debugging

    Amey-Thakur/AI-SKILLS/skills/embedded-iot/embedded-debugging Skill

    14★ repo

    Debug firmware with JTAG/SWD workflows, console-free logging, and hard-fault analysis that names the faulting line. Use when a device crashes, hangs, or misbehaves only in the field.

  • Js error handling

    Amey-Thakur/AI-SKILLS/skills/javascript-typescript/js-error-handling Skill

    14★ repo

    Handle errors in JavaScript and TypeScript with proper Error subclasses, cause chains, and a policy for async and unhandled failures. Use when designing error handling or debugging lost stack traces and swallowed errors.

  • Node backend setup

    Amey-Thakur/AI-SKILLS/skills/javascript-typescript/node-backend-setup Skill

    14★ repo

    Bootstrap a Node.js backend with ESM, typed config, graceful shutdown, and structured logging from the start. Use when starting a Node service or hardening one that grew without foundations.

  • Agent oncall triage

    Amey-Thakur/AI-SKILLS/skills/multi-agent-teams/agent-oncall-triage Skill

    14★ repo

    Run alert triage as agents that dedup the storm, rate severity by user impact, match a runbook, and draw a hard human-escalation line. Use when you want incoming alerts sorted and enriched by an agent team before they reach the on-call engineer.

  • Python error handling

    Amey-Thakur/AI-SKILLS/skills/python/python-error-handling Skill

    14★ repo

    Design exception hierarchies, catch narrowly, and preserve error context so failures stay diagnosable. Use when structuring errors in a Python library or application, or cleaning up broad except blocks.

  • Audit logging

    Amey-Thakur/AI-SKILLS/skills/security/audit-logging Skill

    14★ repo

    Record security-relevant events in a tamper-evident, append-only log that answers who did what and when. Use when building or reviewing logging for authentication, authorization, privilege changes, or access to sensitive data.

  • Vulnerability triage

    Amey-Thakur/AI-SKILLS/skills/security/vulnerability-triage Skill

    14★ repo

    Score incoming vulnerability reports the same way every time, tie each score to a fix deadline, and run disclosure on a predictable clock. Use when a vulnerability report arrives or when standing up a process to handle them.

  • Rust error handling

    Amey-Thakur/AI-SKILLS/skills/systems-languages/rust-error-handling Skill

    14★ repo

    Design Rust error types with the thiserror/anyhow split, context chains, and a deliberate panic policy. Use when structuring errors in Rust libraries and applications.

  • Assertion libraries

    Amey-Thakur/AI-SKILLS/skills/testing/assertion-libraries Skill

    14★ repo

    Pick an assertion style and write checks that fail with a message you can diagnose without a debugger. Use when test failures read as "expected true, got false" and you cannot tell what actually broke.

  • Build fix

    ngocsangyem/MeowKit/.claude/skills/build-fix Skill

    14★ repo

    Build error triage: detect language, load fix patterns, auto-retry. Use for 'build failed', 'fix compilation', 'type error'. Chains into mk:verify. NOT for runtime errors (see mk:fix); NOT for architectural debugging (see mk:investigate).

  • Investigate

    ngocsangyem/MeowKit/.claude/skills/investigate Skill

    14★ repo

    Systematic debugging with root cause investigation. Produces a diagnostic report; mk:fix owns remediation and mk:build-fix owns compile/build failures. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively suggest when the user reports errors, unexpected behavior, or is troubleshooting why something stopped working. NOT for applying fixes without investigation (see mk:fix); NOT for step-by-step evidence-based reasoning (see mk:sequential-thinking).

  • Mk build fix

    ngocsangyem/MeowKit/packages/mewkit/src/migrate/modules/codex/root/.agents/skills/mk-build-fix Skill

    14★ repo

    Build error triage: detect language, load fix patterns, auto-retry. Chains into mk:verify. NOT for runtime errors (mk:fix); NOT for architecture debugging (mk:investigate).

  • Mk investigate

    ngocsangyem/MeowKit/packages/mewkit/src/migrate/modules/codex/root/.agents/skills/mk-investigate Skill

    14★ repo

    Systematic root-cause debugging that produces a diagnostic report (mk:fix applies the fix; mk:build-fix owns compile failures). Use for 'debug this', 'why is this broken', 'root cause'.

  • Mk build fix

    ngocsangyem/MeowKit/packages/mewkit/src/migrate/modules/cursor/root/.cursor/skills/mk-build-fix Skill

    14★ repo

    Build error triage: detect language, load fix patterns, auto-retry. Chains into mk:verify. NOT for runtime errors (mk:fix); NOT for architecture debugging (mk:investigate).

  • Mk investigate

    ngocsangyem/MeowKit/packages/mewkit/src/migrate/modules/cursor/root/.cursor/skills/mk-investigate Skill

    14★ repo

    Systematic root-cause debugging that produces a diagnostic report (mk:fix applies the fix; mk:build-fix owns compile failures). Use for 'debug this', 'why is this broken', 'root cause'.

  • Rails debugging

    Shoebtamboli/rails_claude_skills/lib/generators/claude/skills_library/rails-debugging Skill

    14★ repo

    Use when debugging Rails issues - provides Rails-specific debugging tools (logs, console, byebug, SQL logging) integrated with systematic debugging process

  • Vcp root cause check

    Z-M-Huang/vcp/plugins/vcp/skills/vcp-root-cause-check Skill

    14★ repo

    Analyze a proposed bug fix against VCP root cause analysis standards. Determines whether a fix addresses the root cause or just patches a symptom.

  • Alfresco debugger agent

    aborroy/aiup-alfresco/.cursor/skills/alfresco-debugger-agent Skill

    14★ repo

    Given an Alfresco stack trace or log snippet, searches documentation and known issues to diagnose the root cause and suggest a fix. Covers classloader issues, model registration errors, Transform Service failures, and common ACS problems.

  • Diagnose

    markoblogo/abvx-agent-skills/skills/diagnose Skill

    14★ repo

    Debug coding failures through reproduction, ranked hypotheses, narrow fixes, and verification. Use when a bug, regression, flaky test, performance failure, or inconsistent behavior is broken, slow, throwing, or hard to reproduce and the task needs disciplined diagnosis instead of guessed fixes.

  • Repo debugging ledger

    markoblogo/abvx-agent-skills/skills/repo-debugging-ledger Skill

    14★ repo

    Debug repositories with a hypothesis ledger, checked locations, and loop-breaking discipline. Use when tests fail, CI fails, behavior regresses, local tooling errors, flaky bugs appear, or an investigation risks repeated searches, repeated commands, circular hypotheses, or unverified fixes.

  • Repo issue triage

    markoblogo/abvx-agent-skills/skills/repo-issue-triage Skill

    14★ repo

    Triage bugs, enhancements, and backlog items through a small state machine that works with or without a formal issue tracker. Use when reviewing incoming requests, preparing work for an agent, deciding whether more info is needed, or keeping a multi-project backlog healthy.

  • Shell output compaction

    markoblogo/abvx-agent-skills/skills/shell-output-compaction Skill

    14★ repo

    Reduce shell and tool-output token waste by preferring targeted commands, diff-only views, error-first logs, narrow slices, counts, and concise summaries instead of large raw stdout dumps. Use on coding, debugging, audits, CI triage, or repo exploration when command output is likely to dominate token usage.

  • Ml debugging

    param087/agent-ml-skills/skills/ml-debugging Skill

    14★ repo

    Use when a model won't learn, loss is NaN, metrics look too good/bad, or training is unstable. Provides a systematic decision tree for diagnosing data, optimization, and generalization failures.

    The same file is in 1 other repository

  • Error handling patterns

    marcioaltoe/claude-craftkit/plugins/architecture-design/skills/error-handling-patterns Skill

    14★ repo

    Error handling patterns including exceptions, Result pattern, validation strategies, retry logic, and circuit breakers. **ALWAYS use when implementing error handling in backend code, APIs, use cases, or validation logic.** Use proactively for robust error handling, recovery mechanisms, and failure scenarios. Examples - "handle errors", "Result pattern", "throw exception", "validate input", "error recovery", "retry logic", "circuit breaker", "exception hierarchy".

  • Triage

    isak102/neowright/.agents/skills/triage Skill

    14★ repo

    Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

    The same file is in 14 other repositories

  • Diagnose

    hungv47/meta-skills/skills/research/diagnose Skill

    14★ repo

    Structured diagnosis of business and strategic problems — builds MECE logic trees, forms testable If/Then/Because hypotheses, scans external factors, and identifies root causes with evidence. Use when a metric is underperforming, something went wrong, or you need to find what's causing a problem before acting. Not for code bugs (use clean-code), brainstorming solutions to a known problem (use prioritize), or scoping a new idea (use discover); for market trends, see research-market.

  • B8c9d0e1 f2a3 4b5c 8d9e 8f9a0b1c2d3e

    onurkanbakirci/awesome-skills/public/skills/b8c9d0e1-f2a3-4b5c-8d9e-8f9a0b1c2d3e Skill

    no license14★ repo

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

    The same file is in 30 other repositories

  • Agent introspection debugging

    onfire7777/universal-ai-skills-library/skills/agent-introspection-debugging Skill

    14★ repo

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

    The same file is in 1 other repository

  • Business health diagnostic

    onfire7777/universal-ai-skills-library/skills/business-health-diagnostic Skill

    14★ repo

    Diagnose SaaS business health across growth, retention, efficiency, and capital. Use when preparing a business review or prioritizing urgent fixes.

  • Causal inference root cause

    onfire7777/universal-ai-skills-library/skills/causal-inference-root-cause Skill

    14★ repo

    Use when investigating why something happened and need to distinguish correlation from causation, identify root causes vs symptoms, test competing hypotheses, control for confounding variables, or design experiments to validate causal claims. Invoke when debugging systems, analyzing failures, researching health outcomes, evaluating policy impacts, or when user mentions root cause, causal chain, confounding, spurious correlation, or asks "why did this really happen?"

  • Chrome devtools

    onfire7777/universal-ai-skills-library/skills/chrome-devtools Skill

    14★ repo

    Browser debugging, performance profiling, and automation via Chrome DevTools MCP. Use when user says "debug this page", "take a screenshot", "check network requests", "profile performance", "inspect console errors", or "analyze page load". Do NOT use for full E2E test suites (use playwright-skill) or non-browser debugging.

  • Debug root cause

    onfire7777/universal-ai-skills-library/skills/debug-root-cause Skill

    14★ repo

    Systematic root-cause debugging — reproduce, isolate, hypothesize, fix the actual cause not symptoms. Use when something is broken, behaving unexpectedly, or when a bug needs methodical investigation. Triggers on: 'debug this', 'why is this broken', 'this isn't working', 'find the bug', 'root cause', 'troubleshoot', 'figure out why', 'diagnose this error'.

  • Debugging code

    onfire7777/universal-ai-skills-library/skills/debugging-code Skill

    14★ repo

    Interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running program, and navigate the call stack to trace root causes. Use when a program crashes, raises unexpected exceptions, produces wrong output, when you need to understand how execution reached a certain state, or when print-statement debugging isn't revealing enough.

  • Debugging strategies

    onfire7777/universal-ai-skills-library/skills/debugging-strategies Skill

    14★ repo

    Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.

  • Detecting sql injection via waf logs

    onfire7777/universal-ai-skills-library/skills/detecting-sql-injection-via-waf-logs Skill

    14★ repo

    Analyze WAF (ModSecurity/AWS WAF/Cloudflare) logs to detect SQL injection attack campaigns. Parses ModSecurity audit logs and JSON WAF event logs to identify SQLi patterns (UNION SELECT, OR 1=1, SLEEP(), BENCHMARK()), tracks attack sources, correlates multi-stage injection attempts, and generates incident reports with OWASP classification.

  • Diagnose

    onfire7777/universal-ai-skills-library/skills/diagnose Skill

    14★ 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

  • Error handling patterns

    onfire7777/universal-ai-skills-library/skills/error-handling-patterns Skill

    14★ repo

    Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.

  • Five agent ci debug

    onfire7777/universal-ai-skills-library/skills/five-agent-ci-debug Skill

    14★ repo

    Use when five-agent-dev-team GitHub Actions, Gitleaks, Docker, audit, lint, test, or formatting checks fail.

  • Langsmith fetch

    onfire7777/universal-ai-skills-library/skills/langsmith-fetch Skill

    14★ repo

    Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.

    The same file is in 10 other repositories

  • Postmortem

    onfire7777/universal-ai-skills-library/skills/postmortem Skill

    14★ repo

    Use when analyzing failures, outages, incidents, or negative outcomes, conducting blameless postmortems, documenting root causes with 5 Whys or fishbone diagrams, identifying corrective actions with owners and timelines, learning from near-misses, establishing prevention strategies, or when user mentions postmortem, incident review, failure analysis, RCA, lessons learned, or after-action review.

  • Python error handling

    onfire7777/universal-ai-skills-library/skills/python-error-handling Skill

    14★ repo

    Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.

  • Scout

    onfire7777/universal-ai-skills-library/skills/scout Skill

    14★ repo

    Bug investigation, root cause analysis (RCA), reproduction step identification, and impact assessment. A specialized investigative agent that determines "why it happened" and "where to fix it." Does not write code. Used when bug investigation or root cause analysis is needed.

  • Sentry

    onfire7777/universal-ai-skills-library/skills/sentry Skill

    14★ repo

    Inspect Sentry issues, summarize production errors, and pull health data via the Sentry API (read-only). Use when user says "check Sentry", "what errors in production?", "summarize Sentry issues", "recent crashes", or "production error report". Requires SENTRY_AUTH_TOKEN. Do NOT use for setting up Sentry SDK, configuring alerts, or non-Sentry error monitoring.

  • Skill debugger

    onfire7777/universal-ai-skills-library/skills/skill-debugger Skill

    14★ repo

    Deep dual-model debugging of AI skills using reasoning model and fast synthesis model. Use when asked to debug a skill, find bugs in a skill, review a skill for issues, fix a broken skill, or audit a skill's quality. Also use when a skill is not working correctly or producing unexpected results.

  • Systematic debug

    onfire7777/universal-ai-skills-library/skills/systematic-debug Skill

    14★ repo

    Systematic debugging techniques for unclear root causes. Use when a bug's origin is unknown, multiple hypotheses need testing, you need to narrow down a failing area, end-to-end tests fail but you can't tell where, or the user says "I don't know why this is broken". Includes test bombs (hypothesis elimination) and layered tests (pipeline stage isolation).

  • Systematic debugging

    onfire7777/universal-ai-skills-library/skills/systematic-debugging Skill

    14★ repo

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

  • Thinking five whys plus

    onfire7777/universal-ai-skills-library/skills/thinking-five-whys-plus Skill

    14★ repo

    Enhanced root cause analysis with explicit bias guards and stopping criteria. Use for incident post-mortems, bug investigations, and process failures where standard 5 Whys might mislead.