CtrlK
BlogDocsLog inGet started
Tessl Logo

debugger

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

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/debugger/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 content is a compact, well-organized instruction-only skill with a clear sequenced debugging workflow and verification step, but it lacks concrete executable code or commands and carries some boilerplate filler.

Suggestions

Add at least one executable example, e.g. a strategic logging snippet or a command to run a failing test in isolation, to lift actionability.

Turn the verification step into an explicit feedback loop: 'If the fix fails, re-isolate and retry' rather than a single 'Verify solution works' step.

Remove generic boilerplate ('Apply relevant best practices and validate outcomes') that adds no debugging-specific signal.

DimensionReasoningScore

Conciseness

The body is reasonably tight and assumes Claude's competence, but generic lines like 'Clarify goals, constraints, and required inputs' and 'Apply relevant best practices and validate outcomes' are boilerplate padding that could be trimmed.

3 / 5

Actionability

It lists concrete-sounding steps ('Capture error message and stack trace', 'Add strategic debug logging') but provides no executable code, commands, or concrete tooling, so the guidance is high-level hints rather than copy-paste instructions.

3 / 5

Workflow Clarity

There is a clear sequenced workflow ('When invoked: 1…5') plus a parallel debugging process, and step 5 ('Verify solution works') acts as a checkpoint; minor gaps are the absence of an explicit failure/retry loop.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no bundle files present, and content is organized into well-labeled sections (Use when / Do not use / Instructions / process / deliverables), so the simple-skill exception applies and structure is clean.

5 / 5

Total

15

/

20

Passed

Description

65%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 clearly identifies the debugging niche with natural trigger terms and an explicit 'Use when' clause, but it is light on concrete action verbs, leaning on generic phrasing rather than naming specific debugging actions.

Suggestions

Replace the generic 'Use proactively when encountering any issues' with concrete debugging actions, e.g. 'Diagnoses errors, analyzes stack traces, isolates failing tests, and identifies root causes.'

Add common synonyms users actually say (crash, exception, stack trace, failing test) to broaden trigger coverage.

Make the 'when' clause more specific, e.g. 'Use when the user reports an error, a test fails unexpectedly, or code behaves wrongly.'

DimensionReasoningScore

Specificity

It names the domain ('debugging', 'errors, test failures, unexpected behavior') but the only action verbs are the generic 'Use proactively when encountering any issues' — minimal concrete actions, matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

The 'what' is clear ('Debugging specialist for errors, test failures, and unexpected behavior') and a 'when' clause is present ('Use proactively when encountering any issues'), though the 'when' is broad and could be more specific.

4 / 5

Trigger Term Quality

Includes natural terms users would say ('errors', 'test failures', 'issues', 'debugging'), giving good keyword coverage; only minor synonyms are missing (e.g. 'crash', 'exception', 'stack trace').

4 / 5

Distinctiveness Conflict Risk

The debugging niche is fairly distinct from other skills and unlikely to trigger for the wrong skill; only minor overlap risk with general code-review or testing skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
rmyndharis/antigravity-skills
Reviewed

Table of Contents

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.