debugging-strategies

Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.

0.98x

Quality

70%

Does it follow best practices?

Impact

84%

0.98x

Average score across 6 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/developer-essentials/skills/debugging-strategies/SKILL.md

Quality

Content

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

The body is a well-sectioned, highly actionable debugging compendium with executable examples across multiple languages and a clear phased process. Its main weaknesses are verbosity from restating concepts Claude already knows and a monolithic structure that inlines language-specific references instead of offloading them to bundle files.

Suggestions

Trim or remove padding Claude already knows — the Rubber Duck Debugging section, the Scientific Method restatement, the 'Common Debugging Mistakes' list, and the 'Quick Debugging Checklist' of typos/null/scope basics — keeping only what is non-obvious.

Split the per-language tooling references (JavaScript/TypeScript, Python, Go) and the 'Advanced Debugging Techniques' / 'Patterns by Issue Type' catalogs into files under references/ with one-line pointers from SKILL.md, since the skill is monolithic with no bundle files.

Add explicit feedback-loop checkpoints to the Systematic Debugging Process (e.g., 'if the hypothesis is disproved, return to Phase 2 with the new findings') to raise workflow clarity above a flat phase sequence.

Dimension	Reasoning	Score
Conciseness	The ~520-line body extensively explains concepts Claude already knows (Rubber Duck Debugging, the Scientific Method, what console.table/pdb.set_trace do, a 'Quick Debugging Checklist' of typos and null/undefined), matching the 'noticeably verbose; several unnecessary explanations or padded sections' anchor rather than the mostly-efficient anchor (3).	2 / 5
Actionability	Provides copy-paste-ready executable code and commands across JavaScript/TypeScript, Python, and Go (pdb, breakpoint(), cProfile, git bisect, VS Code launch.json, pprof), covering common cases with only minor illustrative-as-opposed-to-complete examples like the trace decorator.	4 / 5
Workflow Clarity	The 'Systematic Debugging Process' is clearly sequenced (Phase 1 Reproduce → 2 Gather Information → 3 Form Hypothesis → 4 Test & Verify) with per-phase checklists; debugging is investigative rather than destructive so the validation cap does not apply, but explicit if-fail-then-retry feedback loops are only implicit, keeping it below the 5 anchor.	4 / 5
Progressive Disclosure	The skill is monolithic with no bundle files (references/scripts/assets absent) and all language-specific tooling and pattern catalogs inlined; section headers provide structure, but per-language debugging references that clearly belong in separate files are not split out, matching the 'some structure but content that should be separate is inline' anchor.	3 / 5
	Total	13 / 20 Passed

Description

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

The description is strong: third-person voice, explicit 'what' and 'when', and natural trigger phrases covering bugs, performance issues, and unexpected behavior. It is slightly broad ('any codebase or technology stack') which raises minor overlap risk and leaves a few synonyms unstated.

Dimension	Reasoning	Score
Specificity	Names several concrete capability areas — 'systematic debugging techniques, profiling tools, and root cause analysis' plus 'track down bugs across any codebase or technology stack' — with only minor gaps, matching the 'lists several specific actions' anchor rather than the 1-2-action anchor (3).	4 / 5
Completeness	It explicitly answers both 'what' (master debugging techniques, profiling, root cause analysis to track down bugs across any stack) and 'when' ('Use when investigating bugs, performance issues, or unexpected behavior') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	'Use when investigating bugs, performance issues, or unexpected behavior' supplies natural phrases users actually say, plus 'debugging', 'profiling', and 'root cause analysis'; a few common variants (crash, error, stack trace) are missing, so it sits just below the comprehensive synonym anchor (5).	4 / 5
Distinctiveness Conflict Risk	Debugging is a recognizable niche with distinct triggers, but the 'any codebase or technology stack' breadth and overlap with profiling/performance or code-review skills keep it just below the minimal-conflict anchor (5).	4 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (528 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: wshobson/agents
Path: plugins/developer-essentials/skills/debugging-strategies/SKILL.md
Commit: d6837ae

Reviewed: about 12 hours 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.