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 single-purpose workflow skill: fully executable commands, explicit validation feedback loops, an approval gate, and disciplined conciseness. The only material weakness is progressive disclosure — the core writing guidance is delegated to two prompt files that are not present in the bundle.
Suggestions
Add the referenced pr-what-prompt.md and release-note-prompt.md to the bundle (e.g. in references/) so the 'Obey ... in this folder' instructions resolve to real files.
If the two prompt files cannot be bundled, inline their essential rules into SKILL.md and drop the dangling references.
State the expected location of the referenced files precisely (e.g. references/pr-what-prompt.md instead of 'in this folder') so discovery does not depend on folder layout.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and imperative throughout — every step is an instruction ("Copy .github/pull_request_template.md to tmp-PR-content.md", "Do not tick the boxes") with zero explanation of concepts Claude already knows. The few rationale lines ("Backticks and `$` in a typed title run as shell code") are safety-critical, not padding, matching the 5 anchor exactly. | 5 / 5 |
Actionability | Fully executable: exact git/gh commands, a runnable Python heredoc CI check, and a copy-paste shell block for title extraction and PR creation, covering both open and not-open PR branches. Matches the 5 anchor — specific commands cover the common cases with no gaps. | 5 / 5 |
Workflow Clarity | Twelve clearly sequenced steps with explicit validation checkpoints and feedback loops: "Fix tmp-PR-content.md until the check passes" (step 8), re-running the check after developer edits (step 10), and the approval gate "Do not continue until the developer writes `approve`". This is a GitHub-publishing operation with permission asked before pushing and validation before submit, matching the 5 anchor. | 5 / 5 |
Progressive Disclosure | The body itself is well organized (Inputs / Steps / Rules) and references are one level deep and clearly signaled ("Obey pr-what-prompt.md in this folder", "Obey release-note-prompt.md in this folder"), but no references/, scripts/, or assets/ directories exist in the bundle, so both referenced prompt files are missing — the disclosed content cannot actually be loaded. Not 4 because the reference structure is incomplete/unverifiable rather than having only minor gaps; not 2 because the in-body structure is good and references are clearly signaled rather than buried. | 3 / 5 |
Total | 18 / 20 Passed |