CtrlK
BlogDocsLog inGet started
Tessl Logo

spec

Write a comprehensive product or engineering specification before implementation. Use when the user asks for `/spec`, PRDs, feature specs, API specs, refactor specs, acceptance criteria, user stories, edge cases, or open decision tracking before code is written.

72

Quality

88%

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 instruction skill with a clear workflow and a ready-to-use output template. The main improvement opportunity is adding a short worked example of a completed spec to lift actionability and reinforce the workflow.

Suggestions

Add a brief, filled-in example spec (one or two sections populated) after the Output Pattern so the intended output shape is unambiguous.

Insert a single review step at the end of the Workflow (e.g., 'Re-read the spec for gaps against the acceptance criteria') to add an explicit checkpoint.

Consider one concrete line showing how an Example Prompt maps onto the Output Pattern sections, bridging the workflow and the examples.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — a one-sentence overview, terse numbered workflow, a default output structure, and three example prompts — with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

It provides a concrete, copy-paste-ready output template (the Output Pattern skeleton) and three concrete example prompts, but stops short of a fully worked example spec, leaving a minor gap versus the fully-executable anchor at 5.

4 / 5

Workflow Clarity

A clear, well-ordered seven-step workflow is present; this is non-destructive authoring so the missing-validation cap does not apply, but there are no explicit review/checkpoint steps, placing it just below the validation-with-feedback-loops anchor at 5.

4 / 5

Progressive Disclosure

At under 50 lines with no need for external references, the content is well-organized into clear sections (Overview, Workflow, Output Pattern, Example Prompts), qualifying for the top anchor under the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

90%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 strong, third-person description that clearly states what the skill does and when to use it, with a rich set of natural trigger terms. Its only weak spot is specificity, since it relies on a single headline action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain and one core action ('Write a comprehensive product or engineering specification') but does not enumerate several distinct concrete actions, so it matches the 'names domain and 1-2 concrete actions, not comprehensive' anchor rather than the multi-action anchor at 4.

3 / 5

Completeness

It explicitly answers both 'what' (write a comprehensive spec before implementation) and 'when' (Use when the user asks for `/spec`, PRDs, feature specs, ...), with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

It lists comprehensive natural trigger terms users would actually say — `/spec`, PRDs, feature specs, API specs, refactor specs, acceptance criteria, user stories, edge cases, open decision tracking — covering synonyms and the slash command, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

The `/spec` slash command and PRD/feature-spec/refactor-spec trigger niche is a clear, distinctive scope with minimal overlap risk against other skills.

5 / 5

Total

18

/

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
eigent-ai/agent-skills
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.