Content
81%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 skill body with explicit validation checkpoints and a complete worked example. Its weaknesses are duplicated policy statements that hurt token efficiency and policy prose that could be split into a reference file for cleaner progressive disclosure.
Suggestions
State the issue-closing exception once (in the Link to an Issue section) and reference it from Prerequisites instead of repeating it nearly verbatim.
Move the detailed issue-acceptance, vouching, and config-docs policy prose into a reference file (e.g., references/pr-policy.md) and keep a short gate + pointer in SKILL.md.
Tighten the dense policy paragraphs (e.g., Verify Contributor Access) into short bullet rules to reduce token cost without losing the repo-specific constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and teaches only repo-specific policy Claude would not know, but the issue-closing exception is stated nearly verbatim twice ("Every PR must close an existing issue, except automated dependency updates and build or flaky-test fixes..." appears in both Prerequisites and Link to an Issue), and several dense policy paragraphs could be tightened. This matches "mostly efficient but includes some unnecessary explanation or could be tightened" rather than the minor-trim level of a 4. | 3 / 5 |
Actionability | Guidance is fully executable with copy-paste-ready commands throughout: "gh pr create --title ... --body ...", "git push -u origin HEAD", "gh repo view OWNER/REPO --json nameWithOwner,viewerPermission", "gh run watch", plus a complete worked example PR with a heredoc body covering the common case. This matches the anchor for fully executable, copy-paste-ready commands with specific examples covering common cases. | 5 / 5 |
Workflow Clarity | The multi-step process is clearly sequenced (verify access → check config docs/agent infra → verify branch state → push → create → monitor) with explicit validation checkpoints ("git branch --show-current" annotated "Should NOT be main", "gh auth status", permission JSON checks), error-recovery guidance ("Resolve failed lookups before proceeding", "Resolve any drift before creating the PR"), and a re-check loop ("Rerun PR Issue Acceptance after linked issue labels change"). PR creation is not a destructive or batch operation, so no cap applies. | 5 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent), and the single file is well-sectioned with one-level-deep, clearly signaled references to CONTRIBUTING.md, SECURITY.md, and the PR template. At ~280 lines it exceeds the simple-skill exemption, and the long inline policy prose (issue acceptance, vouching, config-docs checks) could arguably live in a reference file, matching "good structure; most content appropriately placed; minor organization gaps" rather than the clean overview-plus-references split of a 5. | 4 / 5 |
Total | 17 / 20 Passed |