debugger

Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.

Quality

62%

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/debugger/SKILL.md

Quality

Content

57%

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

The body is short and sectioned with a clear step sequence and verification step, but it leans on generic boilerplate and abstract process descriptions rather than concrete debugging techniques, and lacks an explicit failure-recovery loop.

Suggestions

Remove the generic template filler (the "Use/Do not use this skill when" bullets and the first three Instructions bullets) that adds no debugging-specific signal.

Add concrete techniques instead of abstract verbs, e.g. specific logging patterns, breakpoint/print-statement strategies, or git bisect for 'check recent code changes'.

Make the feedback loop explicit: after 'Verify solution works', state that if verification fails you revisit the hypothesis and re-isolate rather than patching symptoms.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but the templated "Use this skill when / Do not use this skill when" and the first generic Instructions bullets are boilerplate that add no debugging-specific value, fitting 'mostly efficient but includes some unnecessary explanation'.	2 / 3
Actionability	Steps like "Capture error message and stack trace", "Implement minimal fix", and "Add strategic debug logging" are abstract descriptions, but the structured "When invoked" sequence and the "For each issue, provide" deliverables checklist give some concrete guidance, landing at 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	The numbered "When invoked" sequence ends with an explicit "Verify solution works" checkpoint, but the error-recovery feedback loop (what to do when verification fails) is only implicit, matching 'steps listed but validation gaps / checkpoints implicit'.	2 / 3
Progressive Disclosure	The skill is under 50 lines, single-purpose, needs no external references, and uses clearly headed sections, so per the simple-skills note well-organized sections earn a 3 even without bundle files.	3 / 3
	Total	9 / 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 clearly covers both capability and an explicit use-trigger, but relies on a role framing rather than enumerating concrete actions and uses generic trigger language ("any issues") that weakens distinctiveness.

Suggestions

Replace the role framing with concrete actions, e.g. 'Diagnoses errors, analyzes stack traces, isolates test failures, and proposes minimal fixes.'

Broaden trigger terms to natural phrasings users say — bug, crash, exception, failing test — instead of the generic 'any issues'.

Tighten the when-clause to a debugging-specific trigger such as 'Use when an error, crash, or failing test needs root-cause analysis.'

Dimension	Reasoning	Score
Specificity	"Debugging specialist for errors, test failures, and unexpected behavior" names the domain and several concrete targets, but it is a role statement rather than a list of multiple specific actions, so it stops at 'names domain and some actions, not comprehensive'.	2 / 3
Completeness	"Debugging specialist for errors, test failures, and unexpected behavior" states what it does and "Use proactively when encountering any issues" gives an explicit when-trigger, clearly answering both what and when.	3 / 3
Trigger Term Quality	It surfaces natural terms users would say ("errors", "test failures", "unexpected behavior") but misses common debugging variations such as bug, crash, exception, or stack trace, matching 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	Debugging is a recognizable niche, but the trigger "any issues" is overly broad and could overlap with many skills, fitting 'somewhat specific but could still overlap with similar skills'.	2 / 3
	Total	9 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/debugger/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.