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.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A tightly written, well-structured debugging skill that delivers an actionable workflow with explicit validation checkpoints and clean progressive disclosure to verified reference files. Its only weakness is minor conceptual overlap between the loop and the nine-rules sections, which slightly inflates the token budget.

DimensionReasoningScore

Conciseness

The body is lean and imperative with minimal concept-explanation padding, but the Scientific Debugging Loop and Agans' 9 Rules overlap conceptually and a few justificatory sentences (e.g. "The loop exists because human intuition...") could be trimmed.

4 / 5

Actionability

Provides concrete, specific guidance — a red-capable loop checklist with four explicit criteria, a copy-paste diagnosis markdown template, and a likelihood/testability ranking scheme — which is highly actionable for an instruction-only skill, with only minor gaps in executable detail.

4 / 5

Workflow Clarity

The five-step Debugging Workflow is clearly sequenced, the Scientific Debugging Loop is an explicit feedback loop ("repeat from step 2 if refuted"), and the red-capable loop completion criterion acts as an explicit validation checkpoint before proceeding.

5 / 5

Progressive Disclosure

The SKILL.md serves as a concise overview with well-signaled, one-level-deep references to real bundle files (references/feedback-loops.md, references/nine-rules.md), with detail appropriately offloaded rather than inlined.

5 / 5

Total

18

/

20

Passed

Description

78%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.

A well-constructed description that explicitly answers both what the skill does and when to trigger it, using natural user phrasing. It is slightly generic on the "what" side and could add a few more trigger synonyms to fully distinguish itself from adjacent testing/review skills.

DimensionReasoningScore

Specificity

Names the domain ("Systematic debugging") and one concrete method ("applies the scientific method to failures"), but does not enumerate multiple discrete debugging actions, matching the anchor for naming a domain with 1-2 actions that are not comprehensive.

3 / 5

Completeness

Clearly states both what the skill does ("Systematic debugging that applies the scientific method to failures") and when to use it ("Use when the user says...") with concrete trigger phrases, matching the anchor for explicitly answering both what and when.

5 / 5

Trigger Term Quality

Includes several natural user phrases ("debug this", "why is this failing", "help me find the bug"), giving good keyword coverage, but misses common synonyms such as "troubleshoot", "not working", or "it's broken".

4 / 5

Distinctiveness Conflict Risk

Debugging is a clear niche with distinctive triggers, but the skill's own See Also notes overlap with closely related skills (testing, performance, review), indicating minor overlap risk rather than minimal.

4 / 5

Total

16

/

20

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.