CtrlK
BlogDocsLog inGet started
Tessl Logo

vibe-debug

Diagnose and fix a reproducible failure in an existing project. Use for crashes, broken behavior, or failing checks, not greenfield planning.

72

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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-sequenced debugging workflow with explicit validation checkpoints and feedback loops, appropriately concise for a process skill. The only gap is the absence of concrete code or commands, which is acceptable for an instruction-only skill but keeps actionability at 4.

DimensionReasoningScore

Conciseness

The body is a lean ~8-line workflow with no padding or explanation of concepts Claude already knows; every line instructs an action, matching the lean-and-efficient anchor.

5 / 5

Actionability

Steps give concrete, specific guidance ("Record input, expected result, actual result, and environment", "Research authoritative sources for 3–5 plausible fixes") but, being a process skill, include no copy-paste code or commands; this sits at mostly-executable rather than fully-executable.

4 / 5

Workflow Clarity

Five numbered steps form a clear sequence with explicit validation ("Re-run the original reproduction and applicable checks") and a feedback loop ("After two failed attempts at the same error, stop speculative edits"), matching the explicit-checkpoints anchor.

5 / 5

Progressive Disclosure

Under 50 lines, well-organized into numbered steps, with a single one-level reference to `../vibe-verify/SKILL.md`; per the simple-skill guideline this scores 5 with well-organized sections and no nested references.

5 / 5

Total

19

/

20

Passed

Description

87%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 concise, well-targeted description that clearly states both capability and trigger conditions with a useful negative boundary. It is strong across all dimensions, with only minor room for broader synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

"Diagnose and fix a reproducible failure" names two concrete actions and pairs them with specific failure types ("crashes, broken behavior, or failing checks"), matching the several-specific-actions anchor; not a 5 because the action set is narrow (diagnose/fix) rather than comprehensive.

4 / 5

Completeness

It explicitly answers both what ("Diagnose and fix a reproducible failure in an existing project") and when ("Use for crashes, broken behavior, or failing checks, not greenfield planning") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"crashes, broken behavior, or failing checks" are natural phrases a user would say, with a negative trigger ("not greenfield planning"); not a 5 because synonyms and common variants (e.g. "bug", "error", "test failure") are not exhaustively covered.

4 / 5

Distinctiveness Conflict Risk

The scope to a "reproducible failure in an existing project" with an explicit exclusion ("not greenfield planning") carves a clear niche with minimal overlap risk against planning or build skills.

5 / 5

Total

18

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
KhazP/vibe-coding-prompt-template
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.