Content
81%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.
A highly actionable, well-sequenced workflow skill: every step has concrete commands, explicit validation checkpoints, and error-recovery branches. Its main cost is token weight — the store-flag and planning-boundary rules are repeated across sections, and the ~163-line single file inlines edge-case handling that could live in reference files.
Suggestions
State the --store stickiness rule once (in the Store selection section) and refer back to it from steps 2-4 instead of re-explaining flag appending each time.
Consolidate the planning-boundary rule: keep it in the opening Planning boundary section and drop the restatements in step 2 and Guardrails, or shorten those to one-line reminders.
Move the extended root-null / store-declaration error handling (the 'Declared in' / 'Invalid store declaration' branch and the auto-selected vs explicit-request branches) into a reference file linked from a short Project check section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body avoids explaining concepts Claude already knows, but redundancy is more than minor: the --store stickiness rule is restated in the Store selection section and again in steps 2, 3, and 4; the planning boundary is stated three times (opening, step 2, Guardrails); and root-null handling is explained in both Project check and step 2. This matches 'mostly efficient but could be tightened' rather than the 4 anchor's 'minor instances'. | 3 / 5 |
Actionability | Fully executable, copy-paste-ready commands throughout ('openspec new change "<name>"', 'openspec status --change "<name>" --json', 'openspec instructions <artifact-id> --change "<name>" --json'), with named JSON fields to parse (applyRequires, artifacts, resolvedOutputPath) and concrete artifact filenames. Matches the 5 anchor for an instruction-only skill with specific, complete guidance. | 5 / 5 |
Workflow Clarity | Clear numbered sequence (steps 1-7) with explicit validation checkpoints: confirm root before any write, re-run status after each artifact, verify each artifact file exists before proceeding, and error-recovery branches (root:null handling, instruction-delegation fallback, 'stop and tell the user'). A todo-list checklist is specified. Matches the 5 anchor's explicit validation plus feedback loops; the 4 anchor's 'minor validation gaps' does not apply. | 5 / 5 |
Progressive Disclosure | No bundle files exist, and the body is well-organized with clear section headers (Planning boundary, Store selection, Project check, Steps, Output, Artifact Creation Guidelines, Guardrails). Not 5 because at ~163 lines the store/root edge-case handling is inline content that could be split into a referenced file, and there are no well-signaled references; not 3 because structure and placement are good, not merely present. | 4 / 5 |
Total | 17 / 20 Passed |