debugging-code
Interactively debug source code — set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running program, and navigate the call stack to trace root causes. Use when a program crashes, raises unexpected exceptions, produces wrong output, when you need to understand how execution reached a certain state, or when print-statement debugging isn't revealing enough.
99
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates specific debugging capabilities and provides comprehensive trigger conditions. It uses third person voice correctly, lists concrete actions, and explicitly defines when the skill should be activated with natural user language. The description effectively distinguishes itself from related skills like code editing or static analysis.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'set breakpoints, step through execution line by line, inspect live variable state, evaluate expressions against the running program, and navigate the call stack to trace root causes.' | 3 / 3 |
Completeness | Clearly answers both what (interactive debugging with breakpoints, stepping, variable inspection, expression evaluation, call stack navigation) AND when ('Use when a program crashes, raises unexpected exceptions, produces wrong output, when you need to understand how execution reached a certain state, or when print-statement debugging isn't revealing enough'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'debug', 'breakpoints', 'crashes', 'exceptions', 'wrong output', 'call stack', 'print-statement debugging'. These cover common debugging scenarios and terminology. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on interactive debugging with distinct triggers like 'breakpoints', 'step through', 'call stack', 'crashes', 'exceptions'. Unlikely to conflict with general code editing or static analysis skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill document that exemplifies best practices. It's concise yet comprehensive, providing actionable commands with clear workflows and strategic guidance. The debugging mindset section adds valuable meta-guidance without being verbose, and the walkthrough provides concrete examples that demonstrate the full debugging cycle.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence throughout. No unnecessary explanations of basic concepts like what debugging is or how debuggers work—it jumps straight into actionable guidance with every section earning its place. | 3 / 3 |
Actionability | Provides fully executable commands throughout with specific examples. Commands like `dap debug script.py --break script.py:42` are copy-paste ready, and the walkthrough demonstrates concrete debugging sessions with actual output examples. | 3 / 3 |
Workflow Clarity | Clear debugging workflow with explicit decision points (hypothesis formation, breakpoint strategies, when to step vs continue). The walkthrough section demonstrates the complete feedback loop: hypothesis → observe → refine → verify fix → restart to confirm. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from setup to advanced use. Appropriately references external files for advanced techniques and debugger installation without burying essential content, using one-level-deep references like `references/advanced-techniques.md`. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- AlmogBaku/debug-skill
- Commit
d70c9a6
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.