Content
75%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 well-structured, highly actionable single-purpose skill: the procedure is clearly sequenced with explicit pre-flight checks and the tool-call template is copy-paste ready. Its main weaknesses are duplicated title/body guidance across two sections and the absence of error-recovery guidance for a failed tool call.
Suggestions
Consolidate the title and body guidance: have step 3 ('Prepare PR Details') reference the 'Best Practices' section instead of restating the imperative-mood, 72-character, and summary/why/issue-reference rules in both places.
Trim explanations of concepts Claude already knows, such as what a draft PR is ('visible to collaborators but will not show as review-requested') and why 72 characters displays cleanly in GitHub/email.
Add a brief error-recovery step after 'Call the Tool' (e.g., if the tool fails because the head branch is not on the remote, push and retry), completing the feedback loop the workflow otherwise lacks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient procedural prose, but title and body guidance is duplicated between 'Prepare PR Details' and 'Best Practices', and a few passages explain things Claude already knows ('Draft PRs are visible to collaborators but will not show as review-requested until marked ready', 'displays cleanly in GitHub and email notifications'). | 3 / 5 |
Actionability | Fully executable guidance: a copy-paste tool-call template with annotated parameters ('github-pull-request_create_pull_request({title, head, body, base, draft, ...})'), concrete git commands ('git push --set-upstream origin <branch>', 'git add -A && git commit -m "<message>"'), and specific worked examples ('Add retry logic for failed API requests', 'Fixes #123') covering the common cases. | 5 / 5 |
Workflow Clarity | A clear five-step sequence (Gather Information -> Check Uncommitted/Unpushed Changes -> Prepare PR Details -> Call the Tool -> Confirm Result) with explicit pre-flight state checks and user-decision branches, but there is no feedback loop for recovering when the tool call itself fails (e.g., remote branch missing or permission errors), which keeps it below anchor 5. | 4 / 5 |
Progressive Disclosure | No bundle files exist and none are needed for this scope; sections (When to Use, numbered Procedure, Best Practices) are well organized and easy to navigate. Minor gap: the guidance duplicated between the Procedure and Best Practices sections could be consolidated, and at ~92 lines the content is slightly past the simple-skill threshold that would allow a 5 on organization alone. | 4 / 5 |
Total | 16 / 20 Passed |