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 well-crafted procedural skill: fully executable commands, a clearly sequenced workflow with explicit pre-filing validation, and honest handling of failure modes (duplicates, no-network). Its weaknesses are mild — some repetition of the routing rule across steps and inline detail that could be moved to reference files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and prescriptive with no explanation of concepts Claude already knows, but the tracker-vs-public routing rule is restated across Steps 1, 2, 4 and 6, and a few sentences are convoluted ('An issue filed so a pull request this session opens can close it needs no exception.'), leaving minor instances that could be trimmed rather than a fully lean every-token-earns-its-place text. | 4 / 5 |
Actionability | Guidance is fully executable: copy-paste-ready commands for search, label listing, issue creation with complete flags, and Project board manipulation with jq filters, plus concrete title patterns, a body template, a named-faults table, and worked examples in references/examples.md covering the common cases. | 5 / 5 |
Workflow Clarity | Steps 0 through 6 are clearly sequenced with an explicit six-item 'Before running it, check' checklist, a duplicate search before filing, and a no-network fallback path — explicit validation checkpoints match the top anchor, and the destructive/batch cap does not apply since validation is present and the operation is neither batch nor destructive. | 5 / 5 |
Progressive Disclosure | The one bundle reference (references/examples.md) exists and is clearly signaled, and wiki links are one-level deep with the fact restated in the body; however, ~184 lines carry detail such as the gh project board command sequence and label decision rules that could sit in reference files, which is a minor organization gap rather than the ideal clear-overview-with-split-content structure. | 4 / 5 |
Total | 18 / 20 Passed |