specalign

Align spec files with implementation. Detects drift between spec and code, surfaces discrepancies, user decides whether to update spec or code. Use when both a spec file and its implementation are in context.

1.12x

Quality

—

Does it follow best practices?

Impact

92%

1.12x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

100%

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

A well-structured, concise instruction-only process skill with an explicit multi-step workflow, validation checkpoints, and copy-ready templates. It assumes Claude's competence and avoids padding.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout; assumes Claude's competence without explaining what specs or code are, and every section (drift categories, mutation policy, workflow steps) earns its place.	3 / 3
Actionability	Provides concrete executable guidance — specific search globs ('.spec.md', '-spec.md'), a mapping-table format, a copy-ready discrepancy template, and explicit decision options — rather than abstract direction.	3 / 3
Workflow Clarity	Six clearly sequenced steps with explicit validation checkpoints ('run lint/typecheck after changes', 'run them' for existing tests) and a summary with remaining items, matching the top anchor.	3 / 3
Progressive Disclosure	A single-file, well-organized skill (~110 lines) with clear section hierarchy and no bundle files needed; per the simple-skills scoring note this warrants the top score.	3 / 3
	Total	12 / 12 Passed

Description

85%

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, third-person description with an explicit 'Use when' trigger covering both what and when. Trigger-term coverage is solid but slightly narrow, lacking common phrasings users might naturally say.

Suggestions

Broaden trigger terms to include natural user phrasings like 'spec drift', 'specs out of sync', or 'spec out of date' alongside 'spec file and implementation in context'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Detects drift between spec and code, surfaces discrepancies, user decides whether to update spec or code' — matching the highest anchor.	3 / 3
Completeness	Explicitly answers what it does (align/detect/surface/decide) and when to use it ('Use when both a spec file and its implementation are in context'), satisfying the top anchor.	3 / 3
Trigger Term Quality	Has relevant keywords ('spec file', 'implementation', 'drift') but lacks common variations a user might say ('spec drift', 'specs out of sync', 'spec out of date'), so coverage is partial rather than full.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche — spec-vs-implementation drift alignment — with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Commit: 26d37ce

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.