Content
88%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 is a tightly written operational workflow with exact commands, JSON fields to parse, and strong validation/confirmation checkpoints throughout. Its only weaknesses are minor: a few repeated statements (never-edit-code, write-ownership) and a dense preamble that inflates token usage without bundle-file offloading.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with non-obvious operational detail (store stickiness, `root: null` handling, glob artifact rules) and assumes Claude's competence — no basic concepts are explained. However, there is minor redundancy that could be trimmed: "Never edit code" appears in the opening line and again in Guardrails, step 4's "step 5 owns every write" is restated in step 5 ("This step performs every artifact write in this workflow"), and the store-selection paragraph re-explains the flag-append rule twice. This fits the 4 anchor (efficient with minor over-explanation), not 5, since a few sentences genuinely repeat. | 4 / 5 |
Actionability | Guidance is fully executable throughout: exact commands (`openspec status --change "<name>" --json`, `openspec instructions "<artifact-id>" --change "<name>" --json`, `openspec list --json`) with the specific JSON fields to read (`root`, `existingOutputPaths`, `isPlanningComplete`), concrete error-message prefixes to branch on ("Declared in", "Invalid store declaration in"), exact user-facing output requirements, and specific filesystem checks ("a create operation that fails if the target already exists"). This is an instruction-only skill and its guidance is copy-paste actionable, matching the top anchor. | 5 / 5 |
Workflow Clarity | Six clearly sequenced steps with explicit validation checkpoints and feedback loops: the project check reads `root` before any write and interprets a non-zero exit as an answer rather than a failure; glob-file creation re-checks scope/skip status and concrete-path containment immediately before writing; every edit is confirmed with the user before being applied; and failure branches say to stop and reconcile rather than overwrite. This matches the anchor requiring explicit validation steps and error-recovery loops. | 5 / 5 |
Progressive Disclosure | There are no bundle files, and the body is well organized with clearly signaled sections (Store selection, Project check, Input, Steps, Output, Guardrails) and no nested references. This fits the 4 anchor (good structure, minor organization gaps) rather than 5 because the >50-line simple-skill exception doesn't apply and the long store-selection/project-check preamble is dense inline material that could plausibly live in a shared reference; it is not 3 because the content is procedural workflow that must be followed linearly, not bulk reference material wrongly inlined. | 4 / 5 |
Total | 18 / 20 Passed |