Content
68%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.
Highly actionable content: executable commands, minimal-output --jq patterns, and an error-handling table make it immediately usable. Its weaknesses are redundant repetition of the PR-create snippet and a missing validation gate before the destructive merge command, which caps workflow clarity.
Suggestions
Consolidate the three PR-create examples (full workflow, minimal form, and capturing-URL sections) into one authoritative snippet, showing the heredoc form once and referencing it from the workflow.
Add a validation gate before merging: instruct to confirm `gh pr checks` pass and `gh pr view --json reviewDecision,mergeable` is approved/mergeable before running `gh pr merge --squash --delete-branch`.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is command-dense with no padding of concepts Claude already knows, but the heredoc PR-create snippet is duplicated three times (full workflow, minimal form, and capturing-URL sections), which goes beyond minor trimming and warrants tightening. | 3 / 5 |
Actionability | Every section is fully executable, copy-paste-ready commands with exact flags, --jq output filters, a concrete CORRECT/WRONG shell-escaping pair, per-phase body templates, and an error-to-fix table covering the common GitHub operations. | 5 / 5 |
Workflow Clarity | The PR creation sequence is clearly ordered with a duplicate-PR check and error-recovery table, but the destructive merge operation (gh pr merge --squash --delete-branch) has no validation gate such as confirming gh pr checks pass or reviewDecision before merging; the rubric's destructive-operation cap of 3 applies despite the otherwise clear sequence. | 3 / 5 |
Progressive Disclosure | The skill is a single self-contained file with no bundle references, and the ~200-line body is well organized with clear section headers; the inline convention tables are compact and appropriately placed, though the per-phase templates and conventions could arguably live in a references file at this length. | 4 / 5 |
Total | 15 / 20 Passed |