Content
92%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.
An excellent operational runbook: fully executable commands, a clearly numbered workflow with stop conditions and verification at every risky step, and proactive delegation of the changelog sub-task to a sibling skill. The only weakness is slight repetition across sections that could be tightened.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense, command-first operational content with no padding about concepts Claude already knows; the explanatory asides (FETCH_HEAD staleness, CI flag semantics) are non-obvious gotchas that earn their place. Minor trimmable repetition remains — prerelease handling is explained in both §3 and §5, and remote resolution appears in both Prerequisites and Conventions. | 4 / 5 |
Actionability | Every step ships a copy-paste command with exact flags ('gh release create ... --prerelease', 'git show FETCH_HEAD:Cargo.toml | grep ...'), and placeholders like <remote> and <verified-release-sha> are defined with resolution/verification commands. Fully executable guidance covering the common cases. | 5 / 5 |
Workflow Clarity | Clearly sequenced §0–§6 with explicit validation checkpoints ('must equal the version being released, or stop', 'stop if it differs'), verify commands after each outward-facing step, a failure rollback path with double confirmation, and conditional handling for latest vs non-latest releases. The destructive rollback includes show-before-delete guidance, so no cap applies. | 5 / 5 |
Progressive Disclosure | A well-organized self-contained runbook with no bundle files; all content is needed for the single release flow, and it actively delegates the heavy changelog process to the clearly-signaled sibling 'greptimedb-release-note' skill — an appropriate one-level-deep split. Section structure makes navigation easy. | 5 / 5 |
Total | 19 / 20 Passed |