debugging

Systematic debugging frameworks for finding and fixing bugs - includes root cause analysis, defense-in-depth validation, and verification protocols

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/debugging/SKILL.md

Quality

Content

50%

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

The content is a well-organized index/dispatch skill with clear routing, but it carries motivational padding, lacks executable guidance in the body, and references sub-skill files that are absent from the bundle.

Suggestions

Remove or condense the 'Core Philosophy' quote and time/percentage statistics to improve token efficiency.

Either include the referenced sub-skill SKILL.md files in the bundle or note explicitly that they are external, so progressive disclosure navigation is not broken.

Add a brief in-body validation checkpoint (e.g., 'verify fix with fresh test run before claiming done') to strengthen workflow clarity rather than relying entirely on sub-skill delegation.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and avoids explaining concepts Claude knows, but the 'Core Philosophy' quote and debugging-time statistics ('15-30 minutes to fix', '95% vs 40%') are motivational padding that could be trimmed.	2 / 3
Actionability	Provides concrete routing (sub-skill locations, a dispatch table, and iron-law rules like 'NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST') but no executable code or commands in the body itself, fitting the 'some concrete guidance but incomplete' anchor.	2 / 3
Workflow Clarity	Symptom-to-sub-skill routing is clear via the 'When to Use' list and dispatch table, but the body delegates actual sequenced steps and validation checkpoints to the sub-skills rather than presenting an explicit in-body sequence with feedback loops.	2 / 3
Progressive Disclosure	References to sub-skill SKILL.md files are clearly signaled and one level deep, but the referenced paths (systematic-debugging/SKILL.md, etc.) do not exist in the bundle, so navigation is incomplete.	2 / 3
	Total	8 / 12 Passed

Description

67%

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 specific and distinctive, but it omits an explicit 'Use when...' trigger clause and lacks common natural trigger terms, leaving the when-half of completeness implied rather than stated.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when encountering test failures, errors, or unexpected behavior' so completeness is not capped at 2.

Broaden trigger terms to include natural phrasings users say such as 'test failures', 'errors', 'broken code', and 'exceptions'.

Consider merging the when_to_use content into the description so the trigger guidance travels with the description field.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('finding and fixing bugs', 'root cause analysis', 'defense-in-depth validation', 'verification protocols'), matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Clearly states what the skill does but the description has no 'Use when...' trigger clause; the when-guidance lives only in the separate when_to_use field, so completeness caps at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Contains some relevant natural keywords ('bugs', 'fixing bugs') but misses common variations users would actually say like 'test failures', 'errors', 'broken', or 'exceptions'.	2 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (systematic debugging frameworks) with distinct triggers in third person, unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: mrgoonie/claudekit-skills
Path: .claude/skills/debugging/SKILL.md
Commit: 80113d8

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