Content
67%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content delivers a clear, well-structured stance with concrete CLI commands and a useful capture table, scoring well on actionability and organization. Its weakness is verbosity — repeated guardrails and large illustrative blocks inflate the token budget.
Suggestions
Consolidate the 'Don't implement' rule: state it once in the opening and remove the duplicate 'Don't implement' entry from the Guardrails section to cut tokens.
Trim the large generic ASCII art example under 'Visualize' to one small representative diagram, keeping the stance point without the padding.
Consider folding 'What You Don't Have To Do' into 'The Stance' or removing it, since its points are largely the inverse of already-stated guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient but carries noticeable padding — a large illustrative ASCII diagram block, a 'What You Don't Have To Do' section, and 'Don't implement' restated in Guardrails after the opening — that could be tightened without losing clarity; it is not a 2 because the prose itself assumes Claude's intelligence rather than over-explaining basics. | 3 / 5 |
Actionability | Provides concrete executable commands ('openspec list --json', 'openspec status --change "<name>" --json', 'openspec store list --json', '--store <id>') and a specific insight-to-artifact capture table with example offers; minor gaps (no full status JSON schema walkthrough) keep it just below 5. | 4 / 5 |
Workflow Clarity | Explicitly framed as a stance rather than a fixed workflow, yet the 'When a change exists' path is a clear numbered sequence (resolve/read artifacts, reference naturally, offer to capture, user decides); no destructive/batch validation is required here, so the cap does not apply, but the deliberately open-ended structure leaves some checkpoints implicit rather than a clean 5. | 4 / 5 |
Progressive Disclosure | No bundle files exist, but the single SKILL.md is well-organized into clearly headed sections (Stance, What You Might Do, OpenSpec Awareness, Guardrails) with no nested references and easy navigation; it is not a 5 only because the body runs long (~280 lines) with inline example dialogues that, while useful, make the overview less lean than the anchor ideal. | 4 / 5 |
Total | 15 / 20 Passed |