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.
A dense, highly actionable process skill: exact commands, template paths, linking syntax, and a worked example, carried by a well-sequenced 8-step workflow with strong validation feedback loops around its mutation steps. The only costs are cross-section repetition of the repository-policy and confirmation rules and a conditional second hop from the .hbs outline to its partials.
Suggestions
Consolidate the defer-to-repository-rules guidance, which currently appears in steps 2 and 7, "Repository-policy handoff", and "Safety & constraints", into a single authoritative section to remove repetition (lowest-scoring dimension: conciseness).
State the publish-confirmation rule once — it is duplicated between step 8 ("Do not create or update a PR without explicit user confirmation of that mutation") and the Never list — keeping the safety emphasis in one place.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient and prescriptive with no explanations of concepts Claude already knows, but the defer-to-repository-rules guidance is restated in steps 2 and 7, "Repository-policy handoff", and "Safety & constraints", and the publish-confirmation rule appears in both step 8 and the Never list. | 4 / 5 |
Actionability | Fully executable guidance throughout: copy-paste-ready commands ("gh pr create --base <base> --head <branch> --title \"<title>\" --body-file <draft>"), exact template paths (".github/pull_request_template.md"), exact linking syntax ("closes owner/repo#123" vs "refs owner/repo#123"), and a worked Example section covering the common case. | 5 / 5 |
Workflow Clarity | Eight clearly sequenced steps with explicit validation checkpoints: confirmation before any mutation, read-back after publish ("read the live PR back and run assets/publish-checklist.md"), and an error-recovery loop ("If anything drifted ... fix the draft and re-confirm before editing again"), plus a checklist for the complex publish process. | 5 / 5 |
Progressive Disclosure | Detail is appropriately split into real, clearly signaled one-level references invoked at their point of use with conditions ("Follow references/evidence-sources.md", "use assets/pr-body-outline.md.hbs only", "run assets/publish-checklist.md"); every referenced path exists in the bundle, including the partials the .hbs names. | 5 / 5 |
Total | 19 / 20 Passed |