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.

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 ./skills/debugging-strategies/SKILL.md

The canonical home for this skill is jbvc/debugging-strategies

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 body is cleanly organized into when-to-use, when-not-to-use, and instruction sections, but it relies on high-level direction without specific tools, lacks an explicit verify-and-retry feedback loop, and references a playbook file that is missing from the bundle.

Suggestions

Name specific, concrete tools or commands for each step (e.g., which profiler, how to capture a trace) so the guidance is directly actionable.

Add an explicit verification feedback loop: verify the fix, and if it fails, return to hypothesis formation and retry.

Either create the referenced 'resources/implementation-playbook.md' or remove the dangling reference so progressive disclosure resolves to real content.

Dimension	Reasoning	Score
Conciseness	The instructional bullets are lean and assume Claude's competence, but the opening line ('Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches') is promotional filler that does not earn its place, so it falls short of the level-3 anchor.	2 / 3
Actionability	Guidance is concrete in direction ('Reproduce the issue...', 'Narrow scope with binary search and targeted instrumentation'), but no specific tools, commands, or examples are named, leaving key details incomplete as the level-2 anchor describes.	2 / 3
Workflow Clarity	A sequence is present (reproduce -> hypothesize -> narrow -> verify), but the single 'verify the fix' step is an implicit checkpoint with no feedback loop for when the fix fails, matching the level-2 anchor rather than level 3.	2 / 3
Progressive Disclosure	The body is well-sectioned and points one level deep to 'resources/implementation-playbook.md', but that referenced file does not exist in the bundle, so navigation leads nowhere and the structure cannot reach level 3.	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 well-formed with an explicit 'Use when' trigger and clear statement of what the skill does. It is held back by partial trigger-term coverage and a broad scope that raises some conflict risk with adjacent skills.

Suggestions

Broaden trigger terms to include natural variations users say, such as 'crashes', 'errors', 'stack traces', and 'debugging'.

Tighten the scope claim ('across any codebase or technology stack') to a more distinctive niche to reduce overlap with general troubleshooting skills.

Replace abstract phrasing like 'Master systematic debugging techniques' with a few more concrete actions (e.g., 'reproduce, profile, and isolate root causes').

Dimension	Reasoning	Score
Specificity	Names the debugging domain and several activities ('systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs'), but these read more as domains than a comprehensive list of concrete, copy-paste-ready actions, so it stops short of the level-3 anchor.	2 / 3
Completeness	It answers both what ('Master systematic debugging techniques, profiling tools, and root cause analysis') and when with an explicit trigger clause ('Use when investigating bugs, performance issues, or unexpected behavior'), matching the level-3 anchor.	3 / 3
Trigger Term Quality	It includes natural triggers ('investigating bugs, performance issues, or unexpected behavior') a user would say, but misses common variations like 'crash', 'error', 'stack trace', or 'debugging', so coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	Debugging is a recognizable niche, but 'across any codebase or technology stack' is broad and the triggers could overlap with general troubleshooting or performance-analysis skills, so it is not yet a conflict-free distinct niche.	2 / 3
	Total	9 / 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: rmyndharis/antigravity-skills
Path: skills/debugging-strategies/SKILL.md
Commit: e63f7dd

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