Content
73%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-sequenced, highly actionable workflow with strong validation checkpoints and feedback loops appropriate to a batch artifact-creation task. Its main weakness is token efficiency: several rules are stated twice across the Steps, Artifact Creation Guidelines, and Guardrails sections, and the store/project-check prose could be tightened or moved out of the main line of the workflow.
Suggestions
Deduplicate the guidance repeated across Steps, Artifact Creation Guidelines, and Guardrails (context/rules handling, re-reading dependencies, and file-existence verification each appear twice) into a single location.
Tighten the Store selection and Project check paragraphs — they are dense multi-clause sentences; splitting or trimming them would reduce token cost without losing the operational rules.
Consider moving the detailed store-resolution and root-error-handling edge cases into a reference file, keeping the core five-step workflow lean in SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is operational and free of explanations of concepts Claude already knows, but it carries noticeable repetition and padding: the rule that 'context and rules are constraints for YOU, not content for the file' appears in both step 4a and the Artifact Creation Guidelines section, 'read dependency artifacts from disk' is restated in the Guardrails, and the store-selection and project-check paragraphs run long. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' better than the level-4 anchor's 'minor instances.' | 3 / 5 |
Actionability | Provides concrete, executable commands ('openspec new change "<name>"', 'openspec status --change "<name>" --json', 'openspec instructions <artifact-id> --change "<name>" --json'), specifies the JSON fields to parse (applyRequires, artifacts, requires, resolvedOutputPath), and gives a naming example ('add user authentication' → 'add-user-auth'). Minor gaps keep it from fully copy-paste-ready coverage: artifact content is delegated to the CLI's template/instruction fields rather than shown, so the common case is covered indirectly. | 4 / 5 |
Workflow Clarity | A clear numbered 5-step sequence with explicit validation checkpoints and feedback loops for a batch operation: check the project root before any write, re-run 'openspec status --change "<name>" --json' after creating each artifact, verify each artifact file exists before proceeding, and explicit stop conditions for the required set (done, skipped, or deliberately skipped). This matches the level-5 anchor's 'explicit validation steps; feedback loops for error recovery' for a batch workflow. | 5 / 5 |
Progressive Disclosure | A single-file skill with no bundle files (no references/, scripts/, or assets/ exist) and no external references to verify. Content is organized under clear, well-signaled sections (Store selection, Project check, Input, Steps, Output, Artifact Creation Guidelines, Guardrails) with nothing buried or nested. It falls short of a clean 5 only because the lengthy store-selection and error-handling prose is inlined where a reference file could keep the core workflow leaner — a minor organization gap matching the level-4 anchor. | 4 / 5 |
Total | 16 / 20 Passed |