Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- DebuggerDebugging specialist for errors, test failures, and unexpectedVotes: 0GitHub stars: 508
- DebugTroubleshoot and debug issues. Use when the user reports an error, a test failure, unexpected behavior, or asks to investigate why something isn't working.Votes: 0GitHub stars: 36
- DebugStructured debugging session — reproduce, isolate, diagnose, and fix.Votes: 0GitHub stars: 3
- DebugDebug a stubborn bug with a deterministic reproduction, hypothesis ledger, one-variable fixes, and a regression test. Use after the first obvious look fails, reproduction is unclear, or a fix attempt failed. Not for routine obvious failures; use for "ไล่บั๊ก".Votes: 0GitHub stars: 6
- DebuggingRoot cause analysis and debugging protocols. Use when encountering errors, test failures, unexpected behavior, stack traces, or when code behaves differently than expected.Votes: 0GitHub stars: 21
- Systematic DebuggingSource: obra/superpowersVotes: 0GitHub stars: 3
- Debugger<!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT --> --- name: debugger description: Debugging specialist for errors, test failures, and unexpected ---Votes: 0GitHub stars: 31
- Debugger<!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT --> --- name: debugger description: Debugging specialist for errors, test failures, and unexpected tags: [debugging, testing] ---Votes: 0GitHub stars: 31
- DebugUse when encountering any bug, test failure, build break, or unexpected behavior — runs a 4-phase systematic debugging process before proposing any fix. Iron Law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST. Produces a `.orchestrator/debug/` artifact the fixer agent must reference.Votes: 0GitHub stars: 53
- Systematic DebuggingInvestigate a failure with an unclear cause, repeated unsuccessful fixes, or a cross-component boundary. Use existing reproduction evidence for a localized bug; not a mandatory multi-stage ritual for every edit.Votes: 0GitHub stars: 2,785
- DebugSystematic debugging via logs, health checks, hypothesis-driven investigation. Triggers: debug, error, trace root cause, fix bug, reproduce symptom, investigation.Votes: 0GitHub stars: 177
- Systematic Debugging4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.Votes: 0GitHub stars: 3
- Superpowers DebugSystematic debugging: reproduce, isolate, form hypotheses, instrument, fix, and add regression tests. Use when troubleshooting errors, failing tests, or unexpected behavior.Votes: 0GitHub stars: 3
- Debugger'Debugging specialist for errors, test failures, and unexpectedVotes: 0GitHub stars: 46,327
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesVotes: 0GitHub stars: 860
- 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