CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill with executable commands, a worked debugging loop, and clean progressive disclosure into real reference files. The main weakness is conceptual padding in the mindset sections that restates knowledge Claude already has.

Suggestions

Trim 'The Debugging Mindset' and 'Forming a Hypothesis' to skill-specific guidance, dropping general debugging aphorisms Claude already knows.

Collapse the overlap between 'Starting a Session' strategies and 'Setting Breakpoints Strategically' to reduce redundancy and token cost.

Consider a short numbered quick-start sequence at the top so the workflow reads as a gated checklist rather than a reference manual.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but sections like 'The Debugging Mindset' and 'Forming a Hypothesis' restate general debugging wisdom Claude already knows ('Two strikes, rethink', 'Set breakpoints instead of prints') and could be trimmed.

3 / 5

Actionability

Dense with copy-paste-ready commands (`dap debug`, `dap eval`, `dap step`, conditional/invariant breakpoint syntax) and a concrete walkthrough covering the common cases.

5 / 5

Workflow Clarity

Clear progression from Setup through Verify-Your-Fix and Cleanup, with an explicit feedback loop (test the fix in eval, then `dap restart` to confirm). Slightly more reference-manual than gated checklist, so not a 5.

4 / 5

Progressive Disclosure

Overview body points to one-level-deep, clearly signaled references that exist as real files (`references/installing-debuggers.md`, `${CLAUDE_SKILL_DIR}/references/advanced-techniques.md`, `scripts/install-dap.sh`), with advanced bulk content split out appropriately.

5 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that names concrete capabilities and provides explicit 'Use when' triggers tied to recognizable failure modes. The only gap is a few missing natural synonyms a user might say.

Suggestions

Add common synonyms users say, e.g. 'stack trace', 'segfault', or 'core dump', to broaden trigger-term coverage.

Consider mentioning remote/attach scenarios ('attach to a running process') in the description to match the body's coverage.

DimensionReasoningScore

Specificity

Lists multiple 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' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (breakpoints, stepping, inspection, eval, call stack) and 'when' via a concrete 'Use when a program crashes, raises unexpected exceptions, produces wrong output...' trigger clause.

5 / 5

Trigger Term Quality

Includes natural user phrases like 'program crashes', 'raises unexpected exceptions', 'produces wrong output', and 'print-statement debugging', but misses common synonyms such as 'stack trace', 'segfault', or 'core dump'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear interactive-debugging niche with distinctive triggers (breakpoints, call stack, live state) that are unlikely to fire for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
AlmogBaku/debug-skill
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.