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 strong operational reference: fully executable guidance for every PR operation with explicit validation and recovery loops around the destructive merge path. The only weaknesses are repetition of the pr_activity gotcha and the URL shortcut, and a monolithic single-file layout with no progressive split between overview and detail.
Suggestions
State the pr_activity-is-the-only-way-to-read-comments rule once (e.g. in Step 7 plus one bolded callout) and have the tools table, Performance Notes, and Troubleshooting reference it instead of restating it — the same guidance currently appears five times.
Merge the duplicate URL-shortcut guidance: the MCP Tools section and the Performance Notes bullet both explain the url= parameter; keep one and cross-reference it.
Consider splitting the Troubleshooting section (or extended merge/checks detail) into a reference file so SKILL.md stays a lean overview — there are currently no bundle files and all ~285 lines are inlined.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is operational (concrete parameter blocks, zero concept-explanation padding), but the pr_activity/POST-only gotcha is repeated five times (tools table, Step 7, Performance Notes, and two Troubleshooting entries) and the URL shortcut is stated in both the MCP Tools section and Performance Notes — minor over-explanation that could be trimmed. | 4 / 5 |
Actionability | Every operation ships a copy-paste-ready parameter block with concrete values (e.g. 'path: "scheduler/queue.go", line_new: 142', 'decision: "approved" | "changereq"'), and exact accepted values plus the harness_schema tool for body fields are documented — fully executable coverage of the common cases. | 5 / 5 |
Workflow Clarity | Steps 1–10 are clearly sequenced, with explicit validation before the destructive merge ('Set dry_run: true first to preview the merge', 'Use this before merging to confirm required checks are green') and explicit error-recovery loops (drop or re-fetch source_sha on SHA mismatch). The destructive-operation cap does not apply because validation is present. | 5 / 5 |
Progressive Disclosure | Well-organized single file (tools table, numbered steps, examples, performance notes, troubleshooting) that delegates exact JSON schemas to the harness_schema tool instead of inlining them, but at ~285 lines all content is inline with no split between quick-start and deep reference, so it fits anchor 4 rather than anchor 5's 'content appropriately split'. | 4 / 5 |
Total | 18 / 20 Passed |