CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dev-debug

AI DevKit · Guide structured debugging before code changes by clarifying expected behavior, reproducing issues, identifying likely root causes, and agreeing on a fix plan with validation steps. Use when users ask to debug bugs, investigate regressions, triage incidents, diagnose failing behavior, handle failing tests, analyze production incidents, investigate error spikes, or run root cause analysis (RCA).

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

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 tight, well-structured debugging workflow with explicit sequencing, validation checkpoints, and an approval gate; its only weaknesses are minor — slight over-explanation in the rationalizations table and reliance on sibling skills/commands referenced by name without pointers or fallbacks.

Suggestions

Trim the Red Flags table's "Why It's Wrong" column (or merge it into "Do Instead") since the failure-mode reasoning is already evident to Claude, saving tokens without losing the guardrail.

Add a one-line fallback for when `dev-smoke`, `verify`, or `ai-devkit memory` are unavailable (e.g., a plain failing-then-passing test command), so the workflow stays executable outside the full suite.

Include a single worked example of a hypothesis entry showing the predicted evidence, disconfirming evidence, and exact test command format the "Hypothesize and Test" step requires.

DimensionReasoningScore

Conciseness

The body is lean and imperative, but the Red Flags table's "Why It's Wrong" column ("Assumptions skip evidence", "Stack traces show symptoms, not causes") explains failure modes Claude already understands, and the Task Tracing section hedges with "If task tracing is usable" — minor over-explanation that could be trimmed, fitting the score-4 anchor rather than the every-token-earns-its-place level.

4 / 5

Actionability

Two copy-paste-ready commands (`npx ai-devkit@latest memory search/store ...`) and concrete option-comparison criteria (safer/simpler/more scalable) are strong, but sibling tools (`dev-smoke`, `verify`, `task`, `dev-retro`) are invoked by name with no pointer or fallback, and the required per-hypothesis "exact test command or check" is mandated without an example — minor gaps that keep it below fully executable.

4 / 5

Workflow Clarity

A clearly sequenced Clarify → Reproduce → Hypothesize/Test → Plan workflow with explicit validation checkpoints: an approval gate ("Do not modify code until the user approves a selected fix plan"), "Confirm a pre-fix failing signal exists", and post-fix verification via the `verify` skill including regression checks, plus built-in feedback loops through disconfirming evidence.

5 / 5

Progressive Disclosure

A self-contained ~62-line skill with clean sections (Hard Rule, Workflow, Validation, Task Tracing, Red Flags, Output Template); nothing is inlined that belongs in a separate file and no external references are needed, so well-organized sections alone earn the top score.

5 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: it states a concrete multi-step capability set, gives an explicit and extensive 'Use when' clause full of natural synonyms, and defines a distinct debugging niche with no over-claims or filler.

DimensionReasoningScore

Specificity

The description lists four concrete actions — "clarifying expected behavior, reproducing issues, identifying likely root causes, and agreeing on a fix plan with validation steps" — covering the debugging lifecycle end-to-end, matching the comprehensive-coverage anchor rather than the minor-gaps level below it.

5 / 5

Completeness

It explicitly answers both what (the four named actions) and when ("Use when users ask to debug bugs..."), with concrete trigger phrases — the same pattern as the rubric's top completeness example.

5 / 5

Trigger Term Quality

The trigger clause enumerates natural user phrasings with synonyms ("debug bugs, investigate regressions, triage incidents, diagnose failing behavior, handle failing tests, analyze production incidents, investigate error spikes, or run root cause analysis (RCA)"), leaving only trivial variants like "troubleshoot" uncovered.

5 / 5

Distinctiveness Conflict Risk

"Structured debugging before code changes" plus RCA/incident/regression triggers carve a clear debugging niche with distinct triggers and minimal overlap with adjacent testing or verification skills.

5 / 5

Total

20

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

codeaholicguy/ai-devkit

Path

skills/dev-debug/SKILL.md

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.