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

60%

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

Quality

Content

50%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 well-organized into clear trigger, exclusion, instruction, and resource sections, but it suffers from a fluff intro, abstract non-executable guidance, implicit-only validation checkpoints, and a broken reference to a missing playbook file.

Suggestions

Remove the marketing opener ('Transform debugging from frustrating guesswork...') so the skill starts directly with actionable content.

Make the Instructions executable: name concrete tools/commands (e.g. a profiler invocation, a log-grep pattern, a binary-search instrumentation snippet) rather than only strategic imperatives.

Add an explicit validation/feedback loop such as 'If the fix fails to reproduce-free verification, return to hypothesis formation', and either provide `resources/implementation-playbook.md` or drop the broken reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight bullet lists, but the opening line ('Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches') is pure marketing fluff that assumes no Claude knowledge and pads the token budget, so it is more than a minor trim.	3 / 5
Actionability	The Instructions name a few techniques ('binary search', 'targeted instrumentation', 'controlled experiments') and give imperatives, but they stay at the strategic level with no concrete commands, named profiling tools, or executable examples, leaving key execution details missing.	3 / 5
Workflow Clarity	A rough sequence is present (reproduce -> hypothesize -> narrow -> document/verify) and 'verify the fix' is a checkpoint, but intermediate validation and feedback loops are only implicit (e.g. no 'if hypothesis falsified, form a new one' branch), which matches the anchor with checkpoints missing or implicit.	3 / 5
Progressive Disclosure	Section structure is clean and the reference is clearly signaled one level deep, but the referenced file `resources/implementation-playbook.md` does not exist anywhere in the skill bundle, so the navigation target is broken and discovery fails.	3 / 5
	Total	12 / 20 Passed

Description

70%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 answers both 'what' and 'when' with a clear, explicit trigger clause and good natural keywords. Its main weakness is buzzword-laden over-claims ('Master', 'systematic', 'efficiently', 'any codebase') and abstract capability labels instead of concrete actions.

Suggestions

Replace 'Master systematic debugging techniques, profiling tools, and root cause analysis' with concrete actions the skill performs, e.g. 'Reproduce bugs, form and test hypotheses, narrow scope with binary search, and verify fixes'.

Drop over-claim modifiers ('Master', 'systematic', 'efficiently', 'any codebase or technology stack') to reduce fluff and conflict risk.

Add a few more natural trigger terms such as 'debugging', 'errors', 'crashes', or 'troubleshooting' to broaden keyword coverage toward anchor 5.

Dimension	Reasoning	Score
Specificity	The description names the debugging domain plus a few capability areas ('systematic debugging techniques, profiling tools, and root cause analysis') but stops at abstract topic labels rather than concrete actions, and the over-claim verbs 'Master', 'systematic', 'efficiently', and 'any codebase or technology stack' read as buzzword padding that the guidelines penalize.	3 / 5
Completeness	Both 'what' (master debugging techniques/tools/root cause analysis to track down bugs) and an explicit 'Use when' trigger are present, but the 'what' is described through vague capability labels rather than the concrete actions (reproduce, hypothesize, narrow, verify) that the body actually enumerates, so it falls below the fully concrete anchor 5.	4 / 5
Trigger Term Quality	The 'Use when investigating bugs, performance issues, or unexpected behavior' clause supplies natural terms a user would say, but common synonyms like 'debugging', 'errors', 'crashes', and 'stack traces' are missing, leaving it just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	Debugging is a recognizable niche with a clear trigger ('investigating bugs, performance issues, or unexpected behavior'), but it has minor overlap risk with adjacent skills such as code review, testing, or production-incident response skills.	4 / 5
	Total	15 / 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: rmyndharis/antigravity-skills
Path: skills/debugging-strategies/SKILL.md
Commit: 3eff4af

Reviewed: 23 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.