debugging-wizard

Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting crashes, or performing log analysis, error investigation, or root cause analysis.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Quality

Content

71%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 well-structured skill body with excellent progressive disclosure and strong actionability via real multi-language debugger commands. The main weakness is conciseness: generic MUST DO/MUST NOT DO lists and inline explanations of basic commands add tokens that assume too little of Claude.

Suggestions

Tighten the MUST DO / MUST NOT DO lists: drop obvious debugging platitudes ('Reproduce the issue first', 'Assume you know the cause') in favor of non-obvious skill-specific guidance only.

Trim inline comments that re-explain well-known commands (e.g. git bisect basics, Chrome DevTools attach steps); keep comments for genuinely non-obvious flags/syntax.

Add one or two explicit validation checkpoints in the Core Workflow (e.g. 'Confirm the fix passes regression tests before removing debug code') to push workflow_clarity to 5.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the MUST DO / MUST NOT DO lists restate generic debugging platitudes Claude already knows ('Reproduce the issue first', 'Guess without testing') and inline comments re-explain basic debugger/git-bisect commands, which could be trimmed.	3 / 5
Actionability	Provides concrete copy-paste-ready commands across Python (pdb), Node.js, git bisect, and Go (delve) covering common debugging cases, with the bulk of patterns and fixes appropriately deferred to reference files.	4 / 5
Workflow Clarity	A clear five-step sequence (Reproduce, Isolate, Hypothesize and test, Fix, Prevent) with verify/disprove and verify-solution feedback, but checkpoints are present rather than framed as explicit validation gates.	4 / 5
Progressive Disclosure	Clear overview body with a well-signaled reference table including 'Load When' guidance; all five referenced files (debugging-tools, common-patterns, strategies, quick-fixes, systematic-debugging) exist and are exactly one level deep.	5 / 5
	Total	16 / 20 Passed

Description

100%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.

An exemplary description that explicitly states concrete capabilities, provides comprehensive natural trigger terms, and clearly distinguishes the skill's debugging niche. Every dimension lands at the top anchor with no verbosity or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'Parses error messages', 'traces execution flow through stack traces', 'correlates log entries to identify failure points', 'applies systematic hypothesis-driven methodology to isolate and resolve bugs' — giving comprehensive coverage of the debugging domain.	5 / 5
Completeness	Clearly answers both 'what' (parses/traces/correlates/isolates/resolves bugs) and 'when' via an explicit 'Use when...' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms with synonyms users would actually say — 'investigating errors', 'analyzing stack traces', 'troubleshooting crashes', 'log analysis', 'error investigation', 'root cause analysis'.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear debugging niche with distinct triggers (stack traces, root cause analysis, crashes); minimal conflict risk with related skills like monitoring-expert or test-master.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Jeffallan/claude-skills
Path: skills/debugging-wizard/SKILL.md
Commit: 882ef55

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.