Content
77%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.
An operationally excellent skill body: fully executable commands, exact JSON contracts, and a batch workflow with unusually thorough validation and failure handling. Its weaknesses are length — significant duplication between the steps and the Guardrails section — and the absence of any progressive disclosure, with everything monolithically inlined in one long file.
Suggestions
Move the store-selection and project-check preamble into a shared reference file (e.g. references/store-selection.md) — it is generic OpenSpec workflow boilerplate unrelated to archiving specifically and likely duplicated across sibling skills.
Trim the Guardrails section to only rules not already stated in the steps; items like the target-date rule and 'never archive while a sync is in flight' restate step 3d/8c content nearly verbatim.
Move the conflict-resolution examples and output templates into a reference file to shorten the main body while keeping the step sequence lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient, dense operational specifics that assume Claude's competence and never explain known concepts, but there is real tightening to do: the Guardrails section restates step 3d/8c rules nearly verbatim, and the store-selection/project-check preamble re-explains the same flag rules several times. Not 2 because the verbosity is repetition of genuinely necessary operational detail, not padding or explanations of concepts Claude already knows. | 3 / 5 |
Actionability | Fully executable guidance throughout: exact commands with flags (`openspec list --json`, `openspec status --change "<name>" --json`), exact JSON fields to parse, copy-paste-ready bash for the archive move, concrete conflict-resolution walkthroughs, and complete output templates. Matches the 'copy-paste ready, covers common cases' anchor. | 5 / 5 |
Workflow Clarity | Nine clearly sequenced steps with explicit validation checkpoints for a destructive batch operation: batch validation before any write (step 3), a user confirmation gate (step 7), verify-before-move of synced specs (step 8b), re-checking the archive target immediately before the move, and a post-move nesting check with recovery. Error-recovery loops and a guardrails checklist match the top anchor; the batch-operation validation cap does not apply because validation is extensive. | 5 / 5 |
Progressive Disclosure | The in-body structure is well organized (numbered steps, bold sections, examples, guardrails), but there are no bundle files at all: store-selection and project-check boilerplate, conflict-resolution examples, and output templates that clearly belong in separate reference files are all inlined into a single ~365-line body. Not 2 because navigation within the file is good and sections are clearly signaled; not 4 because content that should be split out is inline with no references. | 3 / 5 |
Total | 16 / 20 Passed |