Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- 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
- 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
- DebugDiagnose the current OMC session or repo state using logs, traces, state, and focused reproductionVotes: 0GitHub stars: 7
- Structured DebugAI DevKit · Guide structured debugging before code changes by clarifying expected behavior, reproducing issues, identifying likely root causes, and agreeing on a fix plan with validation steps. Use when users ask to debug bugs, investigate regressions, triage incidents, diagnose failing behavior, handle failing tests, analyze production incidents, investigate error spikes, or run root cause analysis (RCA).Votes: 0GitHub stars: 1,640
- Smart DebugSystematic debugging methodology — powered by Kodelyth. A step-by-step framework to diagnose any bug confidently across any language or framework. Prevents guess-and-check debugging, traces errors to their root cause, and produces a fix backed by evidence.Votes: 0GitHub stars: 11
- DebuggerSystematic debugging specialist focused on root cause analysisVotes: 0GitHub stars: 61
- Am Agent Code DebuggerSystematically identify, diagnose, and resolve bugs using advanced debugging techniques. Specializes in root cause analysis and complex issue resolution. Use PROACTIVELY for troubleshooting and bug investigation.Votes: 0GitHub stars: 24
- Debugging StrategiesTransform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.Votes: 0GitHub stars: 2
- DebuggingSystematic debugging workflow for Replit projectsVotes: 0GitHub stars: 24
- Debugging StrategiesTransform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.Votes: 0GitHub stars: 31
- Debugging StrategiesTransform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.Votes: 0GitHub stars: 46,327
- Debug ToolDiagnose runtime and application failures.Votes: 0GitHub stars: 6,113
- DebuggerDebugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.Votes: 0GitHub stars: 8
- DebuggingUse when a bug's cause is unknown. Applies a hypothesis-driven method — reproduce, isolate, instrument, prove — instead of speculative edits, and covers profiler, debugger, and log-based investigation.Votes: 0GitHub stars: 26