CtrlK
BlogDocsLog inGet started
Tessl Logo

debug

Reproduce, minimize, localize, identify root cause, and distinguish diagnosis from an authorized fix. Prefer root-cause over symptom patches.

65

Quality

78%

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 ./crates/tui/assets/skills/debug/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 a compact, well-structured debugging playbook that respects token budget and clearly sequences the diagnosis process. Adding brief feedback-loop guidance for when a step fails would push workflow clarity to the top anchor.

DimensionReasoningScore

Conciseness

The body is lean with no padding and no explanation of concepts Claude already knows; every section (When to use, Non-goals, Workflow, Output shape) earns its place.

5 / 5

Actionability

The numbered workflow is a concrete, directive process for an instruction-only skill, but steps like 'Minimize the case' and 'Localize to component/file/line' give little guidance on the specific technique to use.

4 / 5

Workflow Clarity

A clear five-step sequence with an explicit guard ('Fix only when authorized') and an output-shape checklist, but it lacks explicit feedback loops (e.g. what to do when reproduction fails) for error recovery.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, organized into clearly labeled sections — meeting the rubric's simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

18

/

20

Passed

Description

71%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 is specific and concise, naming a clear sequence of debugging actions, but it lacks an explicit 'when to use' trigger clause, which caps its completeness. Adding a 'Use when...' clause with natural trigger terms (bug, crash, flake, regression) would raise both completeness and trigger quality.

Suggestions

Add an explicit trigger clause such as 'Use when diagnosing failures, flakes, crashes, wrong outputs, or regressions' so the description answers both what and when.

Surface the natural trigger terms currently buried in the body (bug, crash, flake, regression) into the description to improve trigger-term coverage.

Consider noting the scope boundary (e.g. diagnosis vs. authorized fix) as a trigger cue to further reduce overlap with general coding skills.

DimensionReasoningScore

Specificity

Lists multiple concrete debugging actions — 'Reproduce, minimize, localize, identify root cause, and distinguish diagnosis from an authorized fix' — giving comprehensive coverage of the debug process.

5 / 5

Completeness

Clearly states what the skill does but has no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural terms like 'Reproduce' and 'root cause', but omits common phrases users actually say (bug, crash, flake, regression), which only appear in the body rather than the description.

4 / 5

Distinctiveness Conflict Risk

Debugging is a recognizable niche and the root-cause-vs-fix framing narrows it, but 'debug' as a trigger still has minor overlap with general coding/fixing skills.

4 / 5

Total

16

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Hmbown/Codewhale
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.