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.
87
83%
Does it follow best practices?
Impact
92%
1.12xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly defines its niche and includes an explicit 'Use when' clause with a specific trigger condition. Its main weakness is moderate specificity—it could enumerate more concrete actions (e.g., comparing function signatures, checking for missing endpoints) and include more natural trigger terms users might use when they need this skill.
Suggestions
Add more concrete action examples such as 'compares function signatures, checks for missing endpoints, identifies renamed parameters' to boost specificity.
Expand trigger terms with natural variations like 'specification', 'out of sync', 'spec outdated', 'code doesn't match spec' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (spec-code alignment) and some actions (detects drift, surfaces discrepancies), but doesn't list multiple concrete actions in detail—e.g., what kinds of drift, what specific operations it performs on specs or code. | 2 / 3 |
Completeness | Clearly answers both what ('Detects drift between spec and code, surfaces discrepancies, user decides whether to update spec or code') and when ('Use when both a spec file and its implementation are in context') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'spec file', 'implementation', 'drift', and 'discrepancies', but misses common natural variations users might say such as 'specification', 'out of sync', 'spec outdated', 'code doesn't match spec', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | The niche of spec-implementation alignment is quite distinct and unlikely to conflict with other skills. The trigger condition ('both a spec file and its implementation are in context') is specific and well-scoped. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides clear, actionable guidance for spec-code alignment. The separation of passive principles (always active) from the explicit workflow is well-designed, the discrepancy format with stable IDs is practical, and the mutation policy provides important safety constraints. The content is lean and respects Claude's intelligence throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. The drift categories are a useful taxonomy Claude wouldn't inherently know, the mutation policy adds real constraints, and the workflow steps are tight without unnecessary explanation of obvious concepts. | 3 / 3 |
Actionability | Provides concrete, specific guidance: exact file patterns to search, a table template for mapping spec to code, a numbered discrepancy format with stable IDs, and explicit decision options (update spec/update code/skip). The output templates are copy-paste ready. | 3 / 3 |
Workflow Clarity | Six clearly sequenced steps with explicit validation checkpoints: lint/typecheck after code changes, running unit tests if they exist, confirming before non-trivial edits, and a summary step that tracks resolution status. The feedback loop of presenting discrepancies → user decision → apply changes is well-defined. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections (Principles vs Workflow), but everything is inline in a single file. For a skill of this length (~100 lines), this is acceptable, but the Principles section could potentially be separated or the drift categories could reference a more detailed guide for complex cases. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
e437c3c
- 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.