Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- DebugDebug some featureVotes: 0GitHub stars: 33
- DebuggerDebugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.Votes: 0GitHub stars: 23
- DebugDebugging command. Activates DEBUG mode for systematic problem investigation.Votes: 0GitHub stars: 3
- Common DebuggingTroubleshoot systematically using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions.Votes: 0GitHub stars: 549
- Mode DebugDebug mode: observe, hypothesize, test, evaluate, fix-and-stop; no certainty without evidence, no symptom patches. Load when switching to [debug mode] or when diagnosing a bug or unexpected behavior.Votes: 0GitHub stars: 1,992
- DebuggingDiagnose and repair software failures using evidence, reproduction, instrumentation, and regression tests rather than speculative edits.Votes: 0GitHub stars: 2
- DebuggerDebugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.Votes: 0GitHub stars: 3
- DebuggingSystematic root-cause analysis and problem resolution.Votes: 0GitHub stars: 2
- Common DebuggingSystematic troubleshooting using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions. (triggers: debug, fix bug, crash, error, exception, troubleshooting)Votes: 0GitHub stars: 43
- DebugStructured bug diagnosis and fixing workflow — reproduce, diagnose root cause, apply minimal fix, write regression test, and scan for similar patternsVotes: 0GitHub stars: 4
- Systematic DebuggingDiagnose failures from runtime evidence before editing code.Votes: 0GitHub stars: 14
- DebugStructured bug diagnosis and fix — Root cause analysis, pattern scanning, regression testsVotes: 0GitHub stars: 46
- Common DebuggingStop random edits. They destroy causal information and make it unclear which change helped or whether the bug was merely masked. Reset the debugging process without reverting other people’s work: record the symptom, exact reproduction steps, expected versus actual behavior, environment, and current diff. Preserve the state in a branch or patch if needed. Then: 1. Observe the complete error/stack trace, relevant logs, inputs, timing, recent changes, and dependency/configuration versions. 2. Bu...Votes: 0GitHub stars: 549
- Common DebuggingTroubleshoot systematically using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions.Votes: 0GitHub stars: 549
- Debugging系统化调试 4 阶段Votes: 0GitHub stars: 188
- Debugging系统化调试 — 4阶段强制流程Votes: 0GitHub stars: 188
- DebugSystematic debugging workflow for identifying and fixing bugs. Use when you encounter errors, unexpected behavior, or need to trace through code.Votes: 0GitHub stars: 47
- Debugging MasterySystematic debugging methodology covering root cause analysis, log-based debugging, production debugging, memory leak diagnosis, deadlock detection, performance anomaly investigation, and reproducible bug reproduction. Distilled from real experience at Google, DeepMind, ByteDance, and Huawei. USE WHEN: investigating production incidents, debugging hard-to-reproduce bugs, analyzing crash dumps, finding race conditions, diagnosing memory leaks, debugging performance regressions, or any situati...Votes: 0GitHub stars: 2
- DebugStructured bug diagnosis and fixing workflow — reproduce, diagnoseVotes: 0GitHub stars: 46
- DebuggingDebuggingVotes: 0GitHub stars: 24