Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- DebugfixtureVotes: 0GitHub stars: 8
- 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
- DebuggingDiagnose defects systematically using evidence-driven, technology-agnostic debugging practices.Votes: 0GitHub stars: 3
- 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
- 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
- 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
- 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
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Requires root cause investigation first.Votes: 0GitHub stars: 1,760
- DebuggingTo investigate errors, test failures, and unexpected behavior — root cause before fix.Votes: 0GitHub stars: 352
- Debugging StrategiesTransform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.Votes: 0GitHub stars: 2
- Debugging StrategiesTransform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.Votes: 0GitHub stars: 46,327
- Superstack DebugUse when behavior contradicts expectation — a bug, an unexplained error, a failing test, output that looks wrong, a fix that didn't hold — or when you're about to retry the same category of fix a second time, or work keeps failing or stalling. Also when the user says "debug this", "why is this happening", or "still broken". Skip when the cause is already proven.Votes: 0GitHub stars: 2
- Debugging StrategiesTransform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.Votes: 0GitHub stars: 31
- DebuggingFind 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.Votes: 0GitHub stars: 7
- DebugRun the Resonance **debug** procedure. Read `.agents/skills/engineering/debugger/SKILL.md` in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /debug command to it.Votes: 0GitHub stars: 37
- DebuggingTo investigate errors, test failures, and unexpected behavior — root cause before fix.Votes: 0GitHub stars: 352
- Gsd DebugSystematic debugging with persistent state across context resetsVotes: 0GitHub stars: 10,222
- DebugUse when diagnosing software errors, test failures, or unexpected runtime behaviorVotes: 0GitHub stars: 7