Content
50%Reviews 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-structured, self-contained stance document with some genuinely concrete guidance (an openspec command, file paths, a capture table), but it is verbose for a non-procedural skill and keeps illustrative material inline rather than splitting it into one-level-deep references.
Suggestions
Tighten or consolidate the repeated stance statements across "The Stance", "What You Don't Have To Do", and "Guardrails" to reduce redundancy.
Move the four "Handling Different Entry Points" example dialogues into a separate EXAMPLES.md reference and link to it from the body, improving both conciseness and progressive disclosure.
Promote the concrete capture table and `openspec list --json` command higher as the primary actionable reference, since the surrounding behavioral guidance is the least actionable part.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is well-organized but long (~278 lines) and restates the stance across "The Stance", "What You Don't Have To Do", and "Guardrails", with four verbose example dialogues that could be tightened, matching the anchor for mostly efficient content with some unnecessary explanation. | 2 / 3 |
Actionability | It provides concrete elements (`openspec list --json`, artifact file paths, and an insight-to-artifact capture table), but the bulk of the guidance is behavioral and vague ("Be curious", "Challenge assumptions", "Follow interesting threads"), so it has some concrete guidance but is incomplete as executable instruction. | 2 / 3 |
Workflow Clarity | The "When a change exists" section provides a clear numbered four-step sequence, but the skill is deliberately non-procedural elsewhere and lacks explicit validation/checkpoint steps, matching the anchor for steps listed with implicit or missing checkpoints. | 2 / 3 |
Progressive Disclosure | It is a single monolithic file with no bundle files or external references; internal sections are well-organized, but at ~278 lines (above the 50-line simple-skill threshold) content such as the example dialogues could be split into separate references, matching the anchor for some structure with content that should be separate kept inline. | 2 / 3 |
Total | 8 / 12 Passed |