Content
50%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.
The body is a reasonable high-level catalog of PR-management concerns with a few genuinely useful gh CLI commands and a good PR description template, but it is undermined by pseudocode workflow blocks, absent validation gates for destructive merge operations, and a stray duplicate YAML frontmatter embedded in the markdown. It reads as an agent feature sheet rather than an executable playbook.
Suggestions
Convert the three pseudocode ```bash workflow blocks into real, executable command sequences (actual gh commands per step) or plain numbered prose without the bash fence, and add explicit validation gates such as 'gh pr checks <num> --required' before any merge step.
Move the PR description template and the multi-agent swarm setup into references/ files (e.g. references/pr-template.md, references/review-swarm.md) and link them from the body, keeping SKILL.md as a lean overview.
Delete the second embedded YAML frontmatter block (lines 6-31) or merge its capabilities/hooks into the single top-level frontmatter — the duplicate block is malformed structure and pure token overhead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly tight bullet sections but includes filler Claude does not need ('Handles rollback if needed', 'Maintain clear review SLAs', 'Coordinates with deployment pipelines') and a duplicate/embedded second YAML frontmatter block that adds noise. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not 4 because the stray metadata block and vague filler bullets are genuinely removable. | 3 / 5 |
Actionability | The gh CLI section gives real commands ('gh pr create --title "..." --body "..." --base main', 'gh pr merge --squash --delete-branch'), but the three 'Workflow Patterns' blocks are numbered prose lists wrapped in ```bash fences — pseudocode that is neither executable bash nor concrete steps — and many bullets are abstract ('Handles merge conflicts intelligently'). This matches 'some concrete guidance but incomplete; pseudocode instead of executable code'. | 3 / 5 |
Workflow Clarity | Sequences exist (e.g., 'Standard Feature PR' 1-6) but contain no validation checkpoints or feedback loops — 'Run automated checks' and 'Merge when approved' are mentioned without any verify-then-proceed gate. Since merging and branch deletion are destructive operations, the guideline caps workflow clarity at 3; it is not 2 because the sequences themselves are coherent and ordered. | 3 / 5 |
Progressive Disclosure | The body has clear section headers and no deep nesting, but there are no bundle files at all (references/, scripts/, assets/ are absent) and none are referenced; the PR description template, usage examples, and multi-agent coordination detail all sit inline in a ~180-line monolith. This matches 'some structure but could be better organized'; it is not 4 because content that clearly belongs in separate reference files (templates, swarm setup) is inlined and the stray second frontmatter block muddies navigation. | 3 / 5 |
Total | 12 / 20 Passed |