Content
92%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 tightly written, actionable PR-creation skill with a clear five-phase workflow, explicit validation and stop conditions, and a concrete fallback template. It earns high marks on conciseness and workflow clarity; only the exact `gh pr create` invocation details keep actionability just off the maximum.
Suggestions
Include the concrete `gh pr create --base <base> --head <head> --title ... --body ...` form (and the `--draft` placement) so the creation step is fully copy-paste ready.
Add a short example of the final report line format (PR URL + base <- head + checks) so step 5's output shape is unambiguous.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence: no preamble explaining what a PR or a branch is, every sentence is directive ("Push the current branch...", "Create a ready-for-review PR..."), and it stays well within token budget. | 5 / 5 |
Actionability | It gives concrete executable commands ("gh pr create" with prepared title/body, no interactive editor) and a copy-ready fallback PR template, but omits the exact base/head flags for `gh pr create`, leaving a minor gap in copy-paste readiness. | 4 / 5 |
Workflow Clarity | Five clearly sequenced phases each with explicit validation checkpoints ("Re-read git status and the diff after any commit", "Stop if the branch does not contain the intended work", "Do not report success until GitHub confirms the PR exists"), plus stop-and-ask feedback loops for ambiguity and push rejection. | 5 / 5 |
Progressive Disclosure | No bundle files exist and none are needed at ~100 lines; content is organized into clearly headed sections (Scope, Establish target, Validate, Write PR, Push and create, Verify and report), matching the simple/well-organized-skill exception for a top score. | 5 / 5 |
Total | 19 / 20 Passed |