Content
88%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 dense, highly actionable multi-phase workflow with strong sequencing and validation checkpoints for an outward-facing operation. The main weakness is mild verbosity from embedded rationale and a single-file structure that, while well-organized, is long enough that some material could be split out.
Suggestions
Trim justificatory asides (e.g. 'saves the implementer an hour', 'wastes a round trip') to pure imperatives; the rules already make the constraints clear.
Consider moving the Phase 5 issue-body template and/or the Rules list into a reference file (e.g. references/ISSUE_TEMPLATE.md) and linking to it, keeping SKILL.md as a tighter overview.
A few Phase headings repeat guidance also captured in the Rules section (GH_PAGER=cat, --body-file, /tmp/); consolidate to one authoritative spot to reduce token cost.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient with copy-paste commands and concrete templates, but several justificatory asides ('saves the implementer an hour', 'wastes a round trip', 'reads like a UI breadcrumb and costs characters without adding information') could be trimmed; not a 5 because the rationale padding is noticeable, not a 3 because the core is genuinely lean and actionable. | 4 / 5 |
Actionability | Provides fully executable, copy-paste-ready guidance throughout: `GH_PAGER=cat gh api repos/.../milestones --jq ...`, `gh issue create --title ... --label feature-request --milestone ... --body-file /tmp/<name>.md`, exact JSON data file paths, and a complete body template. | 5 / 5 |
Workflow Clarity | An eight-phase workflow with explicit validation and confirmation gates — 'Do not proceed until both checks pass', 'stop and tell the user before drafting' on duplicate hits, 'Fix anything the check surfaces before posting', confirm before posting, and a verify-and-clean-up phase that reads the issue back and checks all four metadata fields. | 5 / 5 |
Progressive Disclosure | Well-organized into clearly headed sections (Prerequisites, Mission types, Phases 1–8, Rules) with no nested references and no bundle files to misfile; falls short of 5 only because it is a long monolithic single file whose body template or rules block could arguably live in a separate reference. | 4 / 5 |
Total | 18 / 20 Passed |