Content
71%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 well-organized, actionable process doc with concrete helpers, commands, and validation steps. Its main weakness is that the centrally-referenced template.sh is absent from the bundle, which undermines both actionability and navigation.
Suggestions
Ship template.sh in a scripts/ or references/ bundle so the 'copy template.sh' and 'don't edit the library above STAGES' instructions are actually actionable.
Add a short validate→fix→retry feedback loop in the Author/Verify stages for the irreversible operations the skill itself flags (migrations, cutovers).
Tighten the opening prose describing what a wizard is; the helper list and Process section already convey the value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean and assumes Claude's competence — it delegates UX to template.sh rather than re-explaining it — but a few explanatory sentences could still be trimmed. | 4 / 5 |
Actionability | Names concrete library helpers (stage, ask_secret, write_env, set_secret, confirm) and exact commands (bash -n, shellcheck, chmod +x), plus specific files to read; the main gap is that the referenced template.sh is not present in the bundle to copy from. | 4 / 5 |
Workflow Clarity | A clear four-stage sequence (Scope → Map → Author → Verify) with 'Done when' checkpoints and explicit validation (bash -n, shellcheck, static-trace of each value), though it is a verify-by-tracing loop rather than a strict validate→fix→retry cycle. | 4 / 5 |
Progressive Disclosure | Well-structured into clear sections and it signals a one-level-deep reference to template.sh, but that referenced file does not exist in the bundle, so the navigation target is effectively missing. | 3 / 5 |
Total | 15 / 20 Passed |