CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

speckit-clarify

Structured clarification workflow for underspecified requirements. Use before planning to resolve ambiguities through coverage-based questioning. Records answers in spec clarifications section.

57

Quality

72%

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 ./bundled/skills/speckit-clarify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 a well-sequenced, highly actionable workflow with strong validation checkpoints, but it is somewhat verbose for a single file and does not use progressive disclosure to offload the taxonomy and format templates into reference files.

Suggestions

Move the ambiguity/coverage taxonomy into a references file (e.g., taxonomy.md) and summarize the categories inline with a single pointer.

Move the detailed option-table and short-answer output templates into a references file, keeping only the format keys inline.

De-duplicate the question-quota rules (stated in steps 3, 4, and the behavior rules) to a single authoritative statement.

DimensionReasoningScore

Conciseness

The body is mostly necessary instructional content (taxonomy, format templates, integration rules), but the question quota is restated several times (step 3, step 4, behavior rules) and a few tangential notes (single-quote escape syntax) could be trimmed.

3 / 5

Actionability

Provides highly concrete, copy-paste-ready guidance (exact command, JSON fields, output format templates, markdown table, bullet syntax), with only minor interpretation gaps such as 'most appropriate section' mapping.

4 / 5

Workflow Clarity

A clearly sequenced 8-step process with explicit validation checkpoints (step 6 checklist, save-after-each-integration, JSON parse failure aborts) and feedback loops for error recovery on repeated file edits.

5 / 5

Progressive Disclosure

The skill is a single ~175-line file with organized sections but no bundle references; substantial content (the taxonomy and output-format templates) that could live in separate reference files is inlined.

3 / 5

Total

15

/

20

Passed

Description

62%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 clearly communicates the skill's purpose and timing with a concrete 'Use before planning' trigger, but it is not fully comprehensive in its action list or trigger-term coverage.

Suggestions

Add more concrete actions to the what-clause (e.g., 'scan requirements for ambiguity, prioritize and ask up to 5 questions, update the spec clarifications section').

Expand trigger phrases with natural synonyms users would say, such as 'Use when a feature spec is underspecified, ambiguous, or missing acceptance criteria.'

Tighten the 'when' to a more explicit condition rather than only 'before planning'.

DimensionReasoningScore

Specificity

Names the domain ('clarification workflow for underspecified requirements') and a couple of concrete actions ('resolve ambiguities through coverage-based questioning', 'Records answers in spec clarifications section'), but coverage is not comprehensive.

3 / 5

Completeness

Clearly states what the skill does and includes an explicit 'Use before planning' when clause, though the trigger could be more specific (e.g., 'when requirements are ambiguous').

4 / 5

Trigger Term Quality

Contains relevant keywords ('clarification', 'underspecified requirements', 'ambiguities', 'planning') that users may say, but lacks common variations or synonyms and has no file/extension-style natural triggers.

3 / 5

Distinctiveness Conflict Risk

Targets a fairly specific niche (clarification before planning) with distinct triggers, leaving only minor overlap risk with closely related spec/planning skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

foryourhealth111-pixel/Vibe-Skills

Path

bundled/skills/speckit-clarify/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.