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.
The body is highly actionable — every operation has a concrete, executable gh command — and the workflow is clearly sequenced with approval gates and explicit post-create/post-edit verification. Its main weakness is repetition: the no-implementation-detail rule is restated four times and the opening paragraphs duplicate the description, which costs tokens without adding guidance.
Suggestions
State the "no approach, no files, no implementation steps" rule once (the High level, always callout) and let the Don't section reference it instead of repeating it in Before Creating, Refining, and three Don't bullets.
Drop the opening bold paragraphs that restate the frontmatter description, or compress them to a single sentence, keeping only the one-concern rule that isn't already in the description.
Add a brief error-recovery step after the post-create `gh issue view --json` verification (e.g., what to do if the type or state landed wrong) to close the workflow's only validation gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The core no-implementation-detail rule is stated four times ("High level, always… If you catch yourself typing an implementation detail, delete it", "Do not draft an approach. Do not enumerate files… recipe you baked into the body", the Refining bullets, and three Don't entries), and the opening bold paragraphs restate the frontmatter description — mostly efficient, but noticeably tighten-able (anchor 3), not the minor-trims of anchor 4 or the padded verbosity of anchor 2. | 3 / 5 |
Actionability | Fully executable, copy-paste-ready commands cover the common cases: `gh issue create` blocks for both leaf and tracker bodies, `gh issue view --json number,title,issueType,state,url` verification, `gh issue edit --body-file`, and `gh pr create --draft` with the `Closes #<issue-number>` line. This matches anchor 5; anchor 4 would leave gaps in the covered cases, which it doesn't. | 5 / 5 |
Workflow Clarity | The Flow section gives a clear 6-step sequence with explicit checkpoints — "Present the full draft… and wait for Josh's approval of that exact text", "Verify the created issue's number, type, and state" backed by a real verification command after both create and edit. It falls short of anchor 5 because there is no error-recovery feedback loop for when verification shows something wrong landed. | 4 / 5 |
Progressive Disclosure | A single-file skill with well-organized sections, decision tables, a Quick Reference, and one clearly signaled external pointer ("see the `github` skill's Sub-Issues section for the command") — good structure with minor gaps (the Quick Reference table duplicates commands already shown, and at ~230 lines some material could be consolidated). This fits anchor 4 rather than anchor 5's fully split, reference-navigated layout. | 4 / 5 |
Total | 16 / 20 Passed |