spec-builder

Interactive specification builder for autonomous coding projects. Use when users have vague ideas, need help defining requirements, want to create project specs, or before running autonomous-master.

Quality

60%

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 ./skills/spec-builder/SKILL.md

Quality

Content

42%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 body is well-structured as an overview with clear phases and concrete examples, but it is padded by a large ASCII diagram, lacks invocation guidance for its scripts, omits validation checkpoints, and references missing template files while inlining their content.

Suggestions

Replace or trim the ~90-line ASCII flow diagram with a short numbered phase list to cut padding and raise conciseness.

Add explicit invocation examples for the scripts in scripts/ (e.g., how to run spec_builder.py) and a validation checkpoint confirming the generated spec with the user before output.

Either create the missing templates/saas.md, ecommerce.md, social.md, internal.md and move the inlined template blocks into them, or remove the dangling Templates references.

Dimension	Reasoning	Score
Conciseness	Roughly 90 lines are consumed by a decorative ASCII flow diagram and template blocks are inlined, adding padding without proportional value — noticeably verbose per anchor 2, not severe enough for 1 since the prose sections are reasonable.	2 / 5
Actionability	Provides concrete discovery questions, a follow-up trigger table, and example spec outputs, but never shows how to invoke the referenced scripts (spec_builder.py, etc.), leaving key executable detail missing — anchor 3 rather than 4.	3 / 5
Workflow Clarity	The four phases (discovery, elaboration, tech recommendation, output) are clearly sequenced, but there are no validation checkpoints such as confirming the spec with the user before emitting it, fitting anchor 3.	3 / 5
Progressive Disclosure	Scripts and references are signaled one level deep and exist on disk, but the templates/*.md files referenced in the body do not exist and their content is inlined instead of split out, matching anchor 3.	3 / 5
	Total	11 / 20 Passed

Description

78%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 is strong: third-person voice, explicit what-and-when with concrete trigger phrases, and a well-scoped niche. Main weakness is specificity, where the named actions overlap rather than covering a comprehensive set of distinct capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('specification builder') and a few concrete actions ('defining requirements', 'create project specs') that largely overlap, but coverage is not comprehensive — closer to anchor 3 than 4 which expects several distinct actions.	3 / 5
Completeness	Explicitly states what it does ('Interactive specification builder for autonomous coding projects') and gives a clear 'Use when...' clause with concrete trigger phrases, matching the anchor 5 example exactly; not below because both what and when are present and explicit.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('vague ideas', 'defining requirements', 'create project specs') with good coverage, though a few common synonyms are missing, fitting anchor 4 rather than the exhaustive 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a fairly distinct niche tied to 'autonomous coding projects' and 'before running autonomous-master' with minimal conflict risk, but 'project specs' and 'vague ideas' could overlap with general planning skills, so 4 rather than 5.	4 / 5
	Total	16 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/spec-builder/SKILL.md
Commit: 93ed392

Reviewed: 1 day 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.