speckit-checklist

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

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

56%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 content is highly actionable with a clear sequenced workflow and concrete examples, but it is heavily padded through repetition of the same principle and examples, and it is monolithic with no progressive disclosure into bundle files.

Suggestions

Consolidate the repeated 'requirements vs implementation testing' framing into one authoritative section and remove the duplicated example sets in Execution Steps, Required/Prohibited patterns, and Anti-Examples to recover token budget.

Move the example-checklist-types catalog (ux.md, api.md, performance.md, security.md) and the detailed clarifying-question generation algorithm into separate reference files under references/, linked from SKILL.md.

Add an explicit output-validation checkpoint (e.g., 'verify each item starts with Are/Is/Does and references a spec section or [Gap] marker before reporting') to close the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose: the 'test requirements not implementation' principle and the same examples ('prominent display', 'hover states', 'logo image fails to load') are restated 4+ times across the Purpose, Execution Steps, Required/Prohibited patterns, and Anti-Examples sections.	2 / 5
Actionability	Guidance is mostly executable: concrete commands ('check-prerequisites.ps1 -Json'), exact filename formats, explicit item-structure patterns, and many concrete correct/wrong example items with only minor gaps.	4 / 5
Workflow Clarity	A clear numbered 7-step sequence with Pre/Post-Execution hook checks and a prerequisites validation step; minor gaps include no explicit validate-the-output feedback loop, though append-only file handling mitigates destructive risk.	4 / 5
Progressive Disclosure	The skill has section headers but is a monolithic ~360-line file with no bundle files; content such as example-checklist-types and the detailed clarifying-question algorithm that could live in separate reference files is inlined.	3 / 5
	Total	13 / 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 a clear single action and domain but omits any explicit 'when to use' trigger guidance, capping completeness. Trigger-term coverage and distinctiveness are adequate but not strong.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g., 'Use when reviewing spec/requirements quality for a feature, generating a requirements checklist, or validating acceptance criteria coverage.'

List a few concrete sub-actions or output dimensions (e.g., completeness, clarity, consistency, coverage checks) to raise specificity above a single verb.

Include natural synonyms users might say ('spec review', 'requirements quality', 'acceptance criteria') to improve trigger-term quality and distinctiveness.

Dimension	Reasoning	Score
Specificity	The phrase 'Generate a custom checklist' names one concrete action and the domain ('checklist for the current feature based on user requirements'), but coverage is not comprehensive—no enumeration of checklist dimensions or output variations.	3 / 5
Completeness	It has a clear 'what' ('Generate a custom checklist for the current feature based on user requirements') but no 'Use when...' trigger clause, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	'checklist', 'feature', and 'user requirements' are relevant natural keywords, but common variations or synonyms a user might say (e.g., 'spec review', 'requirements quality', 'acceptance criteria') are absent.	3 / 5
Distinctiveness Conflict Risk	'Checklist for the current feature' is a somewhat specific niche, but 'checklist' alone is generic enough that it could overlap with other checklist-generation skills.	3 / 5
	Total	12 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: .claude/skills/speckit-checklist/SKILL.md
Commit: eaa505e

Reviewed: 3 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.