Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- Systematic Debugging4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.Votes: 0GitHub stars: 13
- DebuggingSystematic debugging workflow for production failures and test regressions.Votes: 0GitHub stars: 24
- DebuggerDebugging specialist for errors, test failures, and unexpectedVotes: 0GitHub stars: 1,449
- DebuggerSystematic debugging specialist focused on root cause analysisVotes: 0GitHub stars: 61
- DebugSystematic debugging with hypothesis tracking — reproduce, hypothesize, test, narrow, fix. Never guess-and-check.Votes: 0GitHub stars: 8
- Systematic Debugging4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.Votes: 0GitHub stars: 3
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Implements scientific method for debugging with root cause analysis.Votes: 0GitHub stars: 207
- Systematic DebuggingUse when diagnosing Android app bugs, crashes, regressions, unexpected state, or inconsistent runtime behavior.Votes: 0GitHub stars: 6
- Systematic DebuggingUse for bugs, test failures, or unexpected behavior needing root causeVotes: 0GitHub stars: 24
- developer-debugging-methodologyDEBUGGING METHODOLOGY — extracted from roles.json deepPrompt for developerVotes: 0GitHub stars: 8
- Debugging And ObservabilityComprehensive practitioner guide to debugging, logging, error handling, and production observability (2026): Agans' nine rules, delta debugging, reproducibility imperative, correlation/trace IDs, OpenTelemetry (CNCF graduated May 11 2026), structured logging (slog/Pino/Serilog/structlog), four observability signals (logs/metrics/traces/profiling), eBPF zero-instrumentation telemetry, SLO-based burn-rate alerting, resilience patterns (retries with jitter, circuit breakers, bulkheads), distribu...Votes: 0GitHub stars: 2
- Debugging MentorTeaches systematic debugging skills and problem-solving methodologies. Use when you need help with debugging mentor.Votes: 0GitHub stars: 8
- DebuggerDebugging specialist for root cause analysis and problem resolutionVotes: 0GitHub stars: 81
- DebuggingTroubleshoot and fix bugs systematically. Use when errors occur, tests fail, or unexpected behavior is observed. Covers root cause analysis and debugging strategies.Votes: 0GitHub stars: 34
- Kit DebugForce the guardrails debugging discipline — reproduce first, CAUSE line, failed-attempts ledger, escalation ladder. Use when debugging is flailing, the same fix keeps failing, or asked to debug systematically.Votes: 0GitHub stars: 6
- DebuggingFind the root cause of a bug instead of guessing at it. Use when the user reports something broken, pastes an error or a stack trace, says this used to work, asks why is this happening, why is this failing, or what is wrong with this. Also use to trace how data flows through a codebase, follow a request end to end, or find where a value is being lost or changed. Also fires on: stack trace, traceback, exception, crash, crashed, segfault, null pointer, undefined, regression, reproduce, bisect, ...Votes: 0GitHub stars: 9
- Debugger'Debugging specialist for errors, test failures, and unexpectedVotes: 0GitHub stars: 30,495
- DebugInvestigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced. Use for diagnosis and repair; follow incident authority for live mitigation.Votes: 0GitHub stars: 950
- DebuggingSystematic debugging of issues — use when a test fails, runtime error occurs, unexpected behavior is reported, or an awareness tick produces anomalous resultsVotes: 0GitHub stars: 96
- DebuggerDebugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.Votes: 0GitHub stars: 6