Content
67%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 solid, command-driven guide with a clear pre-flight-to-draft-to-ready workflow and correct emphasis on the project's template and title conventions. Its weaknesses are redundancy — template rules repeated across four sections — and generic gh CLI material (installation, command cheatsheet) that competes with what Claude already knows.
Suggestions
Consolidate the four overlapping template sections ('Description Template', 'Template Accuracy', 'Missing Sections', 'Using Templates for PR Creation') into a single 'PR description template' section.
Delete the 'Additional GitHub CLI PR Commands' cheatsheet and the multi-platform gh installation block — Claude already knows gh; keep at most a one-line prerequisite check.
Clarify how the body is actually produced: copy .github/pull_request_template.md, fill in each section, and pass the filled file via --body-file, rather than passing the raw template path.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Much of the body is tight and actionable, but there is noticeable padding: multi-platform gh installation instructions Claude already knows, and an 'Additional GitHub CLI PR Commands' cheatsheet of generic commands (gh pr list/status/view/checkout) that adds no project-specific value. The template rules are also repeated across four sections ('Description Template', 'Template Accuracy', 'Missing Sections', 'Using Templates for PR Creation'). It is more efficient than anchor 2's padded examples but clearly not the lean anchor 5. | 3 / 5 |
Actionability | Commands are concrete and executable: 'gh pr create --draft --title "✨(scope): Your descriptive title" --body-file .github/pull_request_template.md --base main', 'git status', 'gh pr ready', plus real title examples. Minor gaps keep it below anchor 5: it never shows how to actually fill in the body from the template, and 'gh pr create --body-file .github/pull_request_template.md' passes the unfilled template as the body, which is confusing guidance. | 4 / 5 |
Workflow Clarity | There is a clear sequence — verify gh/auth, check uncommitted changes with 'git status', run the commit skill first, prepare the description from the template, create the draft PR, later convert with 'gh pr ready'. The pre-flight check is a real checkpoint, and PR creation is neither destructive nor batch, so no cap applies. Minor gaps (no post-create verification, some steps duplicated across sections) hold it below anchor 5. | 4 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent), so all content lives in SKILL.md, which is appropriate for a skill of this size and is well organized with clear section headers. The one external pointer, @.github/pull_request_template.md, is clearly signaled and one level deep. It falls just short of anchor 5 because generic gh reference material that belongs outside the skill is inlined. | 4 / 5 |
Total | 15 / 20 Passed |