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 body is a well-organized, actionable stance guide with concrete commands and artifact references rather than abstract prose. Its main weakness is token efficiency — lengthy ASCII diagrams and repeated example transcripts pad a skill whose core guidance is comparatively compact.
Suggestions
Collapse the multi-line ASCII diagram blocks ("What You Might Do", "Handling Different Entry Points") into shorter representative sketches or move several example transcripts into a referenced file to cut token cost.
Consolidate overlapping guidance — "The Stance", "What You Might Do", "Guardrails", and "What You Don't Have To Do" restate the same principles; merge into a single concise list.
Add one explicit end-of-session validation checkpoint (e.g. 'confirm the user wants to capture before writing any artifact') to make the auto-capture guardrail a concrete sequence step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The prose is mostly efficient and avoids explaining basics Claude already knows, but the large ASCII diagram blocks and several long example transcripts repeat the same stance guidance and could be trimmed without losing clarity. | 3 / 5 |
Actionability | Concrete commands (`openspec list --json`), explicit artifact paths (proposal.md, design.md, tasks.md), and example offer phrases give actionable guidance, with only minor gaps in coverage of edge cases. | 4 / 5 |
Workflow Clarity | Though explicitly a stance rather than a fixed workflow, the change-exists case is sequenced (read artifacts, reference naturally, offer to capture, user decides); as a read-only thinking skill it needs no destructive-operation validation checkpoints. | 4 / 5 |
Progressive Disclosure | Content is well sectioned with clear headers and one-level references to OpenSpec artifact paths; no nested references. Some long inline example transcripts could arguably live elsewhere, but the skill stays navigable at ~280 lines with no bundle files. | 4 / 5 |
Total | 15 / 20 Passed |