CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

speckit-analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

Quality

70%

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 ./tools/factory/.claude/skills/speckit-analyze/SKILL.md

The canonical home for this skill is speckit-analyze in RihardsJ/software-factory

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.

A well-structured, highly actionable read-only analysis workflow with a concrete prerequisite gate and precise output specification. Its main weaknesses are redundancy — the hook protocol duplicated verbatim and a repeated $ARGUMENTS section — and the absence of any bundle files to offload that detail.

Suggestions

Deduplicate the extension-hook protocol: state the shared rules once and have the pre/post sections reference them (e.g., 'apply the hook procedure from Pre-Execution Checks with hooks.after_analyze'), or move the hook spec into a references/hooks.md file.

Remove the redundant trailing '## Context / $ARGUMENTS' section (the 'User Input' section at the top already covers it) and drop the stray shell-quoting tip ('I'm Groot') that belongs to the prerequisite-script context, not this skill.

Make the coverage mapping step concrete: specify the exact matching procedure (e.g., 'match FR-/SC- IDs appearing in task descriptions or referenced file paths; list unmatched IDs in the Coverage Summary Table') so the analysis is reproducible.

DimensionReasoningScore

Conciseness

The body is mostly efficient and procedural, but the extension-hook protocol is duplicated nearly verbatim across the pre-execution and post-analysis sections (~80 combined lines), '$ARGUMENTS' appears in two sections ('User Input' at top and 'Context' at bottom), and the stray shell-quoting tip ("I'm Groot") is padding. This matches anchor 3 ('Mostly efficient but includes some unnecessary explanation or could be tightened') rather than anchor 4.

3 / 5

Actionability

Concrete, executable guidance throughout: an exact script invocation ('.specify/scripts/bash/check-prerequisites.sh --json --require-spec --require-tasks --include-tasks'), derived absolute paths, a fully specified report format with table columns and an example row, and explicit severity heuristics. It stops short of anchor 5 because steps like the task-coverage mapping are described abstractly ('inference by keyword / explicit reference patterns') without concrete executable detail.

4 / 5

Workflow Clarity

A clear 9-step sequence with an explicit validation checkpoint (prerequisite check that aborts with instructive error messaging) and graceful zero-issues handling; the operation is strictly read-only, so the destructive/batch validation cap does not apply. It is not anchor 5 because there is no step verifying the report's internal self-consistency (e.g., that coverage metrics match the tables) — a minor validation gap.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but at ~250 lines the duplicated hook machinery (emitted twice, pre and post) is content that clearly belongs in a shared reference file, matching anchor 3 ('Some structure... content that should be separate is inline'). It does not reach anchor 4 given this inlined, repeated bulk with no external references at all.

3 / 5

Total

14

/

20

Passed

Description

65%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.

A specific, distinctive description anchored by concrete artifact names, but it omits any explicit 'Use when' trigger guidance and lists only one composite action. Adding a trigger clause and enumerating the concrete analysis passes (inconsistencies, duplications, ambiguities, coverage gaps) would raise it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to check consistency between spec, plan, and tasks, or after /speckit-tasks completes, before implementation.'

Enumerate the concrete detection actions (inconsistencies, duplications, ambiguities, underspecified items, coverage gaps) instead of the single composite 'consistency and quality analysis'.

Include natural synonyms users would say, such as 'spec', 'specification', 'cross-artifact check', or 'speckit analyze', to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description names its domain precisely ('across spec.md, plan.md, and tasks.md') and gives 1-2 concrete actions ('consistency and quality analysis'), but 'analysis' is a single composite action rather than a list of concrete detections (e.g., inconsistencies, duplications, coverage gaps), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It falls short of anchor 4, which expects several specific listed actions.

3 / 5

Completeness

The 'what' is clear (non-destructive cross-artifact consistency/quality analysis), but the only 'when' signal is the weakly implied sequencing phrase 'after task generation' — there is no explicit 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Strong keyword coverage via the three literal filenames plus 'task generation' and 'consistency', comparable to anchor 4 ('PDF files, forms, document extraction'). It is not anchor 5 because natural synonyms and phrasings users would say ('spec', 'specification', 'check my spec', 'cross-artifact check') are missing.

4 / 5

Distinctiveness Conflict Risk

Naming the three spec-kit artifacts (spec.md, plan.md, tasks.md) creates a clear niche with distinct triggers and minimal conflict risk with other skills, exactly matching anchor 5 ('Clear niche with distinct triggers; minimal conflict risk').

5 / 5

Total

15

/

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

tools/factory/.claude/skills/speckit-analyze/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.