speckit-checklist

Generate custom quality checklists for validating requirements completeness and clarity. Use to create unit tests for English that ensure spec quality before implementation.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/speckit-checklist/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

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

The skill is highly actionable with a clear, well-validated workflow, but it is verbose and repetitive and makes no use of progressive disclosure — everything lives inline in one large file with no reference bundles.

Suggestions

Deduplicate the recurring 'wrong vs right' examples and 'test requirements not implementation' framing so each point appears once; the Purpose, HOW TO WRITE, Example Checklist Types, and Anti-Examples sections repeat the same items.

Move the large example catalogs and category-structure reference material into a references/ file (e.g., examples.md) and link to it from the main workflow, keeping SKILL.md a lean overview.

Tighten the 'Clarify intent' generation algorithm, which is detailed but verbose, into a compact decision rule.

Dimension	Reasoning	Score
Conciseness	Accurate and structured, but heavily redundant: the 'test requirements not implementation' point and the same example items (hover states, prominent display, logo fallback) recur 3–4 times across sections and could be tightened considerably.	2 / 3
Actionability	Provides concrete commands (prerequisite script invocation), exact filename/ID formats (CHK001, [domain].md), and copy-paste-ready item templates with bracketed markers — highly actionable for an instruction-only skill.	3 / 3
Workflow Clarity	Seven clearly sequenced steps with validation checkpoints (JSON parse of prereq script, file-existence checks, ≥80% traceability threshold) and explicit feedback/escalation loops (question limits, defaults when interaction is impossible).	3 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the body is a single ~290-line inline document; the large example catalogs and category structures could be split into reference files but are not, so structure is present but content that should be separate is inline.	2 / 3
	Total	10 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 specific and distinctive with concrete actions and a clear niche, but it lacks an explicit 'Use when...' situational trigger and relies on a non-natural coined metaphor ('unit tests for English'), limiting trigger-term quality and completeness.

Suggestions

Replace 'Use to create unit tests for English...' with an explicit situational trigger such as 'Use when reviewing a spec or planning document for requirements completeness and clarity before implementation.'

Add natural user-facing terms (e.g., 'spec review', 'requirements checklist', 'definition-of-done') alongside the coined metaphor so trigger-term quality matches what users would actually say.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — generating checklists, validating requirements completeness/clarity, and creating 'unit tests for English' for spec quality — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	The 'what' is clear and a 'Use to create...' purpose clause exists, but it states benefit rather than an explicit 'Use when [situation]' trigger, so per the guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Relevant keywords ('quality checklists', 'spec quality', 'validating requirements') appear, but 'unit tests for English' is a coined metaphor a user would not naturally say and common natural phrasings are missing.	2 / 3
Distinctiveness Conflict Risk	The requirements-vs-implementation quality-checklist niche is distinctive and written in third person, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/speckit-checklist/SKILL.md
Commit: f627ab5

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.