debugging-and-error-recovery

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

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 tightly structured debugging workflow with concrete commands, decision trees, and explicit validation checkpoints, assuming Claude's intelligence throughout. It earns full marks across conciseness, actionability, workflow clarity, and organization.

Dimension	Reasoning	Score
Conciseness	Lean and efficient; it assumes Claude's competence and omits explanations of basic concepts, focusing every section on actionable process and concrete examples.	3 / 3
Actionability	Provides copy-paste-ready bash (npm test flags, git bisect), TypeScript regression tests, and decision-tree diagrams with explicit branches, all executable rather than pseudocode.	3 / 3
Workflow Clarity	The numbered six-step triage checklist is explicitly sequenced with feedback loops (reproduce, reduce, fix, guard, verify) and a final verification checklist with validation checkpoints.	3 / 3
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-organized into clearheaded sections (When to Use, Triage Checklist, Error-Specific Patterns, Verification) with no nested references to follow.	3 / 3
	Total	12 / 12 Passed

Description

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.

The description is concise, uses third person, names concrete actions, and provides explicit natural-language triggers for when to invoke the skill. It cleanly answers both what and when with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists concrete actions ('systematic root-cause debugging', 'finding and fixing the root cause', 'systematic approach') rather than vague language; the companion body confirms triage/fix/guard actions.	3 / 3
Completeness	Explicitly answers what it does ('Guides systematic root-cause debugging') and when to use it via two 'Use when...' clauses covering failure scenarios and intent.	3 / 3
Trigger Term Quality	Natural user-facing terms ('tests fail', 'builds break', "behavior doesn't match expectations", 'unexpected error') are exactly what a user would say when they need this skill.	3 / 3
Distinctiveness Conflict Risk	The clear niche of root-cause debugging ('rather than guessing') distinguishes it from general coding or build skills and is unlikely to trigger for unrelated tasks.	3 / 3
	Total	12 / 12 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: addyosmani/agent-skills
Commit: 70b7506

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.