Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- DebuggingDiagnose defects systematically using evidence-driven, technology-agnostic debugging practices.Votes: 0GitHub stars: 3
- DebuggingSystematic root-cause debugging with verification. Use for errors, stack traces, broken tests, flaky tests, regressions, or anything not working as expected. For validating bug reports before fixing, use bug-reproduction-validator agent.Votes: 0GitHub stars: 43
- Debugging WizardUse when isolating a bug or crash from error messages, stack traces, core dumps and logs with a reproduce, isolate, hypothesize, fix and prevent loop in any language. Includes per-language debugger setup, common bug patterns and git bisect strategies; for repairing a whole broken feature use focused-fix.Votes: 0GitHub stars: 21
- DebugStructured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.Votes: 0GitHub stars: 25
- DebuggingSystematic debugging workflow for production failures and test regressions.Votes: 0GitHub stars: 24
- DebuggingDebug failing tests and flaky behaviorVotes: 0GitHub stars: 24
- Systematic DebuggingUse when a verification gate fails and the next fix needs reproducible diagnosis instead of speculative patching.Votes: 0GitHub stars: 6
- DebugSystematically debugs issues using structured diagnosis — reproduce, isolate, identify root cause, and fix. Use when facing bugs, errors, unexpected behavior, or failing tests.Votes: 0GitHub stars: 7
- DebugStructured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.Votes: 0GitHub stars: 45
- DebugStructured debugging session — reproduce, isolate, diagnose, andVotes: 0GitHub stars: 63
- Cad DebugSystematic debugging - hypothesis and symptom tracked in a state file that survives /clear, with a user-gated second-model consult at dead endsVotes: 0GitHub stars: 6
- DebugStructured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.Votes: 0GitHub stars: 63
- Debugging ProSystematic debugging: reproduce, isolate, hypothesize, verify — with tooling for hard bugs. Use when stuck on a bug, flaky failure, or production incident.Votes: 0GitHub stars: 2
- 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
- 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
- Debugger'Debugging specialist for errors, test failures, and unexpectedVotes: 0GitHub stars: 46,327
- DebuggingSystematic debugging workflow for production failures and test regressions.Votes: 0GitHub stars: 24
- DebuggerSystematic debugging specialist focused on root cause analysisVotes: 0GitHub stars: 61