CtrlK
BlogDocsLog inGet started
Tessl Logo

speckit-specify

Create or update the feature specification from a natural language feature description.

47

Quality

51%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/speckit-specify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with explicit sequencing, validation loops, and concrete templates, and is well-organized into clear sections. Its main weakness is conciseness: it re-explains familiar concepts and duplicates the extension-hook instructions.

DimensionReasoningScore

Conciseness

The body is mostly efficient procedural guidance, but it re-explains concepts Claude already knows (e.g. how to make a 2-4 word short name, detailed table-formatting tips like 'spaces around content') and repeats the extension-hook block almost verbatim in Pre-Execution and step 9, so it could be tightened past the level-2 anchor toward the lean level-3 example.

2 / 3

Actionability

It provides concrete, executable steps with specific file paths, commands (mkdir -p, copy templates), JSON payloads, and a fully worked checklist template, matching the level-3 'Fully executable... copy-paste ready' anchor.

3 / 3

Workflow Clarity

The nine-step flow is explicitly sequenced with validation checkpoints and a feedback loop (step 7c re-runs validation up to 3 iterations, caps [NEEDS CLARIFICATION] markers, and only proceeds when passing), matching the level-3 anchor with explicit validation and error-recovery.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is a single-command workflow with well-organized sections (Pre-Execution, Outline, Quick Guidelines); per the scoring notes a simple skill with clear sections and no external references needed can score 3.

3 / 3

Total

11

/

12

Passed

Description

17%

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 states the skill's purpose concisely and in third person, but it omits any explicit 'Use when...' trigger guidance and relies on internal terminology ('feature specification', 'natural language feature description') rather than language a user would naturally say.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to spec out a feature, write a feature spec, or starts the /speckit.specify workflow.'

Swap internal phrasing for natural user terms like 'spec out a feature' or 'turn a feature idea into a specification' to improve trigger-term quality.

List a couple more concrete actions (e.g. 'generate a short feature name, scaffold the spec directory, and validate spec quality') to lift specificity toward 3.

DimensionReasoningScore

Specificity

It names a domain ("feature specification") and one concrete action ("Create or update"), but does not enumerate multiple specific concrete actions, so it sits at the anchor 'Names domain and some actions, but not comprehensive' rather than the multi-action level 3.

2 / 3

Completeness

It states what the skill does but has no 'Use when...' or equivalent explicit trigger guidance for when Claude should invoke it; per the guidelines a missing trigger clause caps completeness at 2, and here 'when' is entirely absent, matching the level-1 'Missing what OR when' anchor.

1 / 3

Trigger Term Quality

The phrasing 'feature specification from a natural language feature description' is technical/skill-internal terminology; a user would more naturally say 'spec out a feature' or 'write a spec', so it lacks the natural keywords of the level-3 anchor and reads as jargon like the level-1 example.

1 / 3

Distinctiveness Conflict Risk

'Create or update the feature specification' is fairly specific to the spec-kit workflow, but without explicit triggers it could overlap with other specification/planning skills, matching the level-2 'Somewhat specific but could still overlap' anchor rather than the clearly-niched level 3.

2 / 3

Total

6

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
unoplatform/uno
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.