Content
70%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 verification workflow with strong validation checkpoints, weakened by redundancy across steps and a monolithic single-file structure that inlines reference-grade detail (delta-matching rules, report templates) instead of splitting it out.
Suggestions
State the removal-only-change rule (REMOVED/RENAMED with no ADDED/MODIFIED) once and reference it from the other steps, instead of restating it in steps 4, 6, and 8.
Move the REMOVED/RENAMED baseline-matching rules and the report format template into a references/ file and link to them, turning SKILL.md into a leaner overview.
Make the codebase-search steps concrete by suggesting a specific method, e.g. Grep for the requirement name or scenario keywords and specific file-glob patterns, rather than 'search codebase for keywords related to the requirement'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body contains no concept-explanation padding and is dense with operational detail, but it repeats key rules across steps (the removal-only-change rule appears in steps 4, 6, and 8; the store-flag shorthand is explained twice in the opening paragraph) and includes long parentheticals like the normalized-name matching rule that could be tightened. | 3 / 5 |
Actionability | Provides copy-paste-ready commands (openspec status/instructions/list with --json flags, git baseline-recovery commands), exact JSON field names to parse, and exact issue/recommendation templates. Minor gap: 'Search codebase for keywords related to the requirement' offers no concrete search method. | 4 / 5 |
Workflow Clarity | Eight clearly numbered steps with explicit validation checkpoints (project root check, '"root": null' branch handling, evidence-availability gates before each check, unavailableTrackingFiles handling) and error-recovery paths such as git baseline recovery with empty-output interpretation. | 5 / 5 |
Progressive Disclosure | A 210-line monolithic file with no references at all; content that would fit separate files (the report format template, the dense REMOVED/RENAMED baseline-matching rules) is inlined, though internal step headers keep it navigable. | 3 / 5 |
Total | 15 / 20 Passed |