Content
100%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.
Excellent instruction-only skill body: copy-ready gh commands, a tightly sequenced workflow with human-in-the-loop validation and safety rules, and clean delegation of detail to one well-signaled external doc. No dimension shows a gap worth penalizing under the rubric.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~36-line body is lean and assumes competence: no GitHub or gh concepts are explained, drafting detail is delegated to the external ticketing doc, and every sentence instructs — matching the 'every token earns its place' anchor with no padding to trim. | 5 / 5 |
Actionability | Gives fully executable commands — `gh auth status`, `gh repo view --json nameWithOwner`, `gh issue create --title <title> --body-file <file> --assignee @me --label <label>`, `gh issue edit <n> --add-label <label>` — and covers the common cases: blockers ("Blocked by #<n>"), parking an issue without the label, and gh missing or not logged in. | 5 / 5 |
Workflow Clarity | Six clearly sequenced steps with explicit checkpoints: an auth check with a recovery path ("ask the person to install it or run `gh auth login`, and wait"), a human approval gate before batch filing ("Show the drafts and wait for the person's yes"), blockers filed first so numbers exist, and refusal handling ("do not work around it: ask the person to run it"). The batch-operation validation cap does not apply since a validation gate is present. | 5 / 5 |
Progressive Disclosure | A short, single-purpose skill with well-organized Steps and Rules sections and no bundle files to split; its single external reference (writing-factory-tickets.md) is one level deep and clearly signaled ("Read it first"), satisfying the simple-skill exception for a top score. | 5 / 5 |
Total | 20 / 20 Passed |