CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

speckit-checklist

Generate a custom checklist for the current feature based on user requirements.

Quality

64%

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-checklist/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 skill body is highly actionable with a well-sequenced eight-step workflow and exact commands, formats, and examples, but it pays for this with substantial internal repetition (the requirements-vs-implementation distinction and hook protocol are each stated multiple times) and no use of progressive disclosure — everything lives inline in one long file. Consolidating the duplicated sections and moving example catalogs to reference files would improve both weak dimensions without losing any executable guidance.

Suggestions

State the 'requirements quality, not implementation testing' principle once (in the purpose section) and delete its re-explanations in step 6, 'Example Checklist Types', and 'Anti-Examples', keeping only a single set of wrong/right examples.

Extract the per-dimension example catalog and the four sample checklists (UX/API/performance/security) into a references/examples.md file, and factor the extension-hook protocol into one shared section or reference file referenced by both Pre- and Post-Execution checks.

Add an explicit post-generation validation step, e.g., re-read the written checklist to confirm ≥80% of items carry a traceability reference and that IDs continue correctly, with a fix-and-retry loop if not.

DimensionReasoningScore

Conciseness

The body is noticeably verbose through heavy duplication rather than generic concept explanation: the 'unit tests for requirements' idea is restated in at least four places (purpose section, step 6 'CORE PRINCIPLE', 'Example Checklist Types', 'Anti-Examples'), examples like 'Is prominent display quantified' and the logo-fallback item appear three times each, and the entire extension-hook protocol is repeated verbatim between the Pre-Execution and Post-Execution Checks. This matches anchor 2 ('noticeably verbose; several unnecessary explanations or padded sections'). It is not score 1 because the content is domain-specific guidance rather than explanations of concepts Claude already knows, and not score 3 because the repetition is substantial enough that the same instructions could be roughly halved.

2 / 5

Actionability

Guidance is fully executable: an exact command ('Run .specify/scripts/bash/check-prerequisites.sh --json --template checklist-template ... and parse JSON for FEATURE_DIR, AVAILABLE_DOCS list, and TEMPLATE_CONTENT'), concrete file-naming rules ('[domain].md', 'ux.md', 'api.md'), explicit ID continuation logic ('if last item is CHK015, start new items at CHK016'), exact item format patterns with wrong/right examples, and per-domain sample checklists (UX, API, performance, security) covering the common cases. This matches the anchor 5 'fully executable; specific examples cover the common cases' — only trivially below would be anchor 4, which requires minor gaps that are not evident here.

5 / 5

Workflow Clarity

The eight Execution Steps form a clear, ordered sequence with concrete checkpoints: a prerequisites script whose JSON output is parsed, an IF EXISTS conditional load of constitution.md, a bounded clarification stage (max five questions with skip rules), explicit append-vs-create file handling that preserves existing content ('Never delete or replace existing checklist content'), a specified error path for unparseable extensions.yml (report the parser error, then continue), and a final Report step. This fits anchor 4 ('clear sequence with most checkpoints present; minor validation gaps'). It falls short of anchor 5 because there is no post-generation validation loop (e.g., verifying the written checklist parses or that traceability coverage ≥80% actually holds), only an aspiration stated as a requirement.

4 / 5

Progressive Disclosure

The body has clear ## section structure but is a ~375-line monolith with no bundle files at all: content that would naturally live one level deep — the extensive examples-by-quality-dimension catalog, the four per-domain sample checklists, the anti-examples section, and the (duplicated) hook protocol — is all inlined in SKILL.md, matching anchor 3 ('some structure but could be better organized; content that should be separate is inline'). It is not anchor 4 because nothing is split out into references, and not anchor 2 because sections are well-labeled and navigable rather than an unstructured dump; the under-50-lines exception to score 5 clearly does not apply.

3 / 5

Total

14

/

20

Passed

Description

50%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 states one concrete capability clearly but omits any usage triggers, leaving both completeness and trigger quality at the midpoint. It also fails to convey the skill's distinctive angle — reviewing requirements quality within a spec-kit project — which raises conflict risk with generic checklist skills.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g., 'Use when the user asks for a checklist, spec review, or requirements-quality review of the current feature.'

Include synonyms and natural variations users would say, such as 'spec review', 'requirements checklist', or 'review criteria'.

Mention the distinguishing context (spec-kit feature specs / requirements quality, not implementation testing) to reduce overlap with generic checklist or QA skills.

DimensionReasoningScore

Specificity

The description names the domain (feature checklists) and one concrete action — 'Generate a custom checklist for the current feature based on user requirements' — but stops there, matching anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive'). It is not score 4 because no additional specific actions are listed (e.g., appending to existing checklists, reviewing requirements quality), and not score 2 because the action named is concrete and contextually qualified rather than generic.

3 / 5

Completeness

The 'what' is stated clearly ('Generate a custom checklist for the current feature'), but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It does not reach anchor 4 because the 'when' is entirely absent rather than merely under-specified, and it exceeds anchor 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Phrases like 'checklist', 'custom checklist', 'feature', and 'user requirements' are natural terms a user might say, but there are no synonyms or common variations (e.g., 'spec review', 'requirements quality', 'review checklist'), matching anchor 3 ('some relevant keywords but missing common variations or synonyms'). It is below anchor 4 because coverage is thin — only 'checklist' and 'requirements' carry trigger weight — and above anchor 2 because these terms are domain-relevant rather than fully generic.

3 / 5

Distinctiveness Conflict Risk

The description is tied to 'the current feature' and 'user requirements', giving it some specificity, but nothing in the text ties it to the spec-kit context, so it could overlap with generic checklist-creation, QA, or task-tracking skills — matching anchor 3 ('somewhat specific but could still overlap with similar skills'). Not anchor 4 because no distinct niche trigger (e.g., 'spec-kit', 'requirements-quality review') is stated; not anchor 2 because it is not wholly generic.

3 / 5

Total

12

/

20

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.

Validation — 14 / 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

RihardsJ/software-factory

Path

.claude/skills/speckit-checklist/SKILL.md

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.