Content
78%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 lean, well-sequenced orchestration skill that delegates a 6-phase module migration to `@migrator` with per-phase validation and approval gates. Its main weakness is actionability: directives like 'Validate build/tsc/tests' and 'Validate conformance' lack the concrete commands and criteria needed to execute them, and no failure-handling loop is specified.
Suggestions
Replace 'Validate build/tsc/tests after each phase' with the actual commands to run (e.g., `npm run build && npx vue-tsc --noEmit && npm test`) so the validation step is executable rather than directive.
Add a failure feedback loop after the validation step, e.g., 'If validation fails: fix the issues introduced in this phase, re-run validation, and only proceed when it passes.'
Specify what Phase 6 'Validate conformance' entails — a checklist of architecture rules from docs/ARCHITECTURE.md or the command that checks them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line is instructive ('Create `src/modules/[name]/` and move files', 'Server state → Vue Query, Client state → Pinia') with no padding or explanation of concepts Claude already knows. The body is ~25 lines and every token earns its place. | 5 / 5 |
Actionability | Concrete specifics exist (file naming patterns, `.types.ts` + `.contracts.ts`, tech mappings like 'Options → script setup'), but no executable commands are given ('Validate build/tsc/tests' names checks without commands) and key details are missing for 'adapter' and 'Validate conformance'. This matches 'some concrete guidance but incomplete; missing key details' rather than level 4, which would require mostly executable guidance with only minor gaps. | 3 / 5 |
Workflow Clarity | A clear numbered sequence (Phases 0–6) with an explicit validation checkpoint ('Validate build/tsc/tests after each phase') and approval gates before each phase. It falls short of level 5 because there is no error-recovery feedback loop (e.g., what to do when validation fails), though validation steps are present so the batch-operation cap of 3 does not apply. | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines, single-purpose, with no bundle files (references/, scripts/, assets/ absent) and no need for external references. Per the rubric's simple-skill exception, the well-organized '## Steps' section alone warrants a 5. | 5 / 5 |
Total | 17 / 20 Passed |