Content
85%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 deploy workflow with strong validation gates. The main gap is progressive disclosure: a bundled reference file is unused and surface detail is inlined.
Suggestions
Link references/surfaces.md from the 'Supported Surfaces' section and move per-surface config/deploy mechanics there, keeping SKILL.md as an overview.
Trim the Step 2b changelog guidelines to the essential rules; the bullet style can be implied from the example.
Consider collapsing the version-handling prose into a short table to reduce token weight.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense and task-oriented, assuming Claude's competence (no explanations of git tags or conventional commits), with a few prose sections like the changelog guidelines that could be tightened. | 4 / 5 |
Actionability | Provides copy-paste-ready bash commands, exact file paths, and fully-specified AskUserQuestion blocks covering the common deploy cases. | 5 / 5 |
Workflow Clarity | Nine numbered steps with explicit validation checkpoints (preflight stop-gate, dry run, CRITICAL user-approval gate before push) and a dedicated error-handling section with recovery guidance. | 5 / 5 |
Progressive Disclosure | Scripts are referenced one level deep via `node scripts/...`, but `references/surfaces.md` exists yet is never linked from the body, and surface-specific deployment mechanics are inlined rather than delegated to that reference. | 3 / 5 |
Total | 17 / 20 Passed |