Content
88%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 workflow: every step has executable commands, validation checkpoints appear before risky operations, and failure paths (patch conflict, gh auth) are handled explicitly rather than left implicit. The main costs are repetition between the steps and the 'Important rules' section and the length of the single-file body.
Suggestions
State the 'return to ORIGINAL_BRANCH before stopping' rule once (e.g., in the Important rules section) instead of repeating it at each early-exit point, and reference it from the steps.
Deduplicate the 'Important rules' section against the step bodies, keeping it to genuinely cross-cutting rules only (never checkout -- file, never apply versioning files, never auto-resolve conflicts).
Consider moving the verbatim commit-message and PR-body templates into a short reference file to slim the main body, since they are pasted verbatim rather than reasoned about.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Nearly every sentence carries skill-specific operational detail (branch naming convention, versioning-file exclusion, the prohibition on 'git checkout <sha> -- <file>'), with no explanation of concepts Claude already knows. Not 5: the 'Checkout ORIGINAL_BRANCH before stopping' clause repeats about five times and the 'Important rules' section restates rules already given in the steps; not 3: the redundancy is deliberate emphasis, not unnecessary explanation. | 4 / 5 |
Actionability | Every step ships copy-paste-ready commands with clearly marked placeholders: 'git rev-parse --verify <COMMIT_SHA>^{commit}', 'git show ... | git apply --index', the full commit-message template, the PR body template, and 'gh pr create' with all flags, plus a concrete fallback path when gh auth fails. Not 4: there are no gaps — both success and failure paths are fully executable. | 5 / 5 |
Workflow Clarity | Steps 0-7 are clearly sequenced with explicit validation checkpoints (SHA resolution, remote ref existence, clean working tree, branch-already-exists check), error-recovery branches (apply failure → Step 7 diagnosis; gh auth failure → manual PR URL), a human-in-the-loop checkpoint (6a pause for versioning), and a closing rules checklist. Not 4: validation is explicit and comprehensive rather than having minor gaps. | 5 / 5 |
Progressive Disclosure | Well-organized single-file structure (Steps 0-7 with lettered subsections, a diagnosis table, a closing rules section) with no dead references, which is appropriate for a linear single-procedure skill with no bundle files. Not 5: at ~330 lines it exceeds the under-50-line simple-skill case, and the inlined commit-message/PR-body templates plus duplicated rules content could be split or deduplicated; not 3: navigation is easy and nothing that clearly belongs in a separate file is buried. | 4 / 5 |
Total | 18 / 20 Passed |