CtrlK
BlogDocsLog inGet started
Tessl Logo

debugging

Systematic debugging that applies the scientific method to failures. Use when the user says "debug this", "why is this failing", "help me find the bug", or is stuck on a problem and thrashing without progress.

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 well-structured, opinionated debugging playbook with strong workflow clarity, explicit validation checkpoints, and clean progressive disclosure into two real reference files. Its main weakness is mild redundancy across the loop, rules, and workflow sections.

Suggestions

Consolidate the overlapping observe→hypothesize→test framing across the Scientific Debugging Loop, Agans' 9 Rules, and the Debugging Workflow to reduce redundancy and tighten conciseness toward a 3.

Consider adding one concrete example invocation of a red-capable loop command (with sample output) to make the completion criterion even more copy-paste ready.

In the Form Hypotheses step, the ranking criteria ('Likelihood', 'Testability') are stated but could include a one-line worked example of ranking to lift actionability further.

DimensionReasoningScore

Conciseness

Dense and opinionated with no padding of concepts Claude already knows, but the Scientific Debugging Loop, Agans' 9 Rules, and Debugging Workflow sections restate observe→hypothesize→test with some redundancy that could be tightened.

2 / 3

Actionability

Provides a concrete Red-capable-loop checklist, ranked hypothesis criteria, an explicit completion criterion, and a copy-paste diagnosis template — actionable guidance throughout, which the rubric accepts for instruction-only skills absent code.

3 / 3

Workflow Clarity

A clearly sequenced 5-step loop with an explicit validation checkpoint ('Do not proceed to hypotheses until you can name one command you have already run') and a self-correcting feedback cue ('If you catch yourself reading code... stop').

3 / 3

Progressive Disclosure

The body signals one-level-deep references to references/feedback-loops.md and references/nine-rules.md, both of which are real bundle files, keeping SKILL.md an overview that points to detail.

3 / 3

Total

11

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it clearly states both what the skill does and when to use it, with natural trigger terms and a distinct niche. The only minor gap is that it frames the capability abstractly rather than listing concrete actions.

DimensionReasoningScore

Specificity

Names the domain ('Systematic debugging') and method ('applies the scientific method to failures') but does not enumerate multiple concrete actions like the score-3 anchor, so it sits at 'names domain and some actions'.

2 / 3

Completeness

Explicitly answers what ('Systematic debugging that applies the scientific method to failures') and when ('Use when the user says...'), matching the score-3 what-and-when anchor.

3 / 3

Trigger Term Quality

Quotes natural user phrasings — "debug this", "why is this failing", "help me find the bug", "thrashing without progress" — giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

A clear debugging niche with distinct, specific triggers that are unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tslateman/duet
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.