CtrlK
BlogDocsLog inGet started
Tessl Logo

test-plan

Produce a focused test plan for a change. Use when the user asks how to test a feature, what cases to cover, or for a QA checklist before shipping.

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.

A tight, well-structured skill body that delivers an actionable process and output template without padding. A worked example and an explicit verification checkpoint would push actionability and workflow clarity to full marks.

Suggestions

Add one short worked example (a real given/when/then case) in the Output format to make the template fully concrete.

Add an explicit validation step such as 'Review the plan against the change to ensure each case maps to a real risk before presenting.'

Consider listing a couple more trigger synonyms (e.g. 'regression cases', 'test coverage') in the description for broader activation.

DimensionReasoningScore

Conciseness

The body is lean and efficient, assuming Claude's competence without explaining what test plans or risks are; every line earns its place.

5 / 5

Actionability

It gives concrete, executable guidance (a numbered process and a copy-paste output template) but the cases are framed as abstract given/when/then placeholders rather than a worked example, leaving a minor gap.

4 / 5

Workflow Clarity

The five-step process is clearly sequenced with an implicit validation checkpoint (step 5 scopes the plan, and 'ask for the acceptance criteria before listing cases' guards unclear input), but it lacks an explicit verify-the-plan checkpoint.

4 / 5

Progressive Disclosure

As a simple, under-50-line single-purpose skill with no need for external references, it is well-organized into Process and Output format sections, qualifying for the simple-skill exception.

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 concise, well-structured description that clearly states both purpose and explicit trigger conditions in third person. Minor room to enumerate more concrete actions and broaden trigger synonyms.

DimensionReasoningScore

Specificity

The description names the domain (test planning) and one concrete action ('Produce a focused test plan for a change') but does not enumerate multiple specific actions like restate, risk-rank, or list cases, leaving coverage non-comprehensive.

3 / 5

Completeness

It explicitly answers both what ('Produce a focused test plan for a change') and when ('Use when the user asks how to test a feature, what cases to cover, or for a QA checklist before shipping') with concrete trigger phrases.

5 / 5

Trigger Term Quality

It includes natural phrases users would say ('how to test a feature', 'what cases to cover', 'QA checklist before shipping'), with only minor common synonyms (e.g. 'test cases', 'regression') missing.

4 / 5

Distinctiveness Conflict Risk

The test-planning niche is mostly distinct with clear triggers, though 'how to test a feature' could mildly overlap with general coding/QA assistance 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.