CtrlK
BlogDocsLog inGet started
Tessl Logo

debug-plan

Create a systematic debugging plan for a bug report. Use when the user asks how to investigate a failure, regression, or unexpected behavior.

68

Quality

82%

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

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 tight, well-structured instruction set that assumes Claude's competence and cleanly offloads detail to a verified reference file. Adding a brief worked example would push actionability to the top level.

DimensionReasoningScore

Conciseness

The body is lean with no padding and no explanation of concepts Claude already knows; every line ("Restate the symptom in one sentence", "Keep the plan short enough that someone can start immediately") earns its place.

5 / 5

Actionability

The five numbered steps are concrete and directive ("List the most likely failure boundaries", "Suggest the first three checks in order"), giving mostly executable guidance; as an instruction-only skill it lacks worked examples, leaving a minor gap.

4 / 5

Workflow Clarity

The steps are clearly sequenced 1-5 from symptom to fix path; this is a planning skill rather than a destructive/batch operation so the validation cap does not apply, though no explicit checkpoints are present.

4 / 5

Progressive Disclosure

The SKILL.md is a concise overview that points to a real, one-level-deep reference ("read `references/checklist.md`", verified present), with content appropriately split and easy navigation.

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.

The description is concise, third-person, and clearly answers both what the skill does and when to use it with natural trigger phrases. It is slightly light on enumerated capabilities, which keeps specificity from the top level.

DimensionReasoningScore

Specificity

"Create a systematic debugging plan" names the domain and one concrete action (producing a plan), but does not enumerate multiple distinct capabilities, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

It explicitly states what ("Create a systematic debugging plan for a bug report") and when ("Use when the user asks how to investigate a failure, regression, or unexpected behavior") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"Use when the user asks how to investigate a failure, regression, or unexpected behavior" surfaces several natural phrases users would say; it lacks a few common synonyms/variations, fitting the 'good coverage, a few terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The debugging-plan niche with triggers like "regression" and "unexpected behavior" is mostly distinct from other skills, with only minor overlap risk against general troubleshooting skills.

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
cloudflare/agents
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.