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.
An exemplary instruction-only skill: a tightly sequenced seven-step workflow where every step is backed by a copy-paste-ready gh command, with explicit validation gates and a red-flags checklist that catch the failure modes (filing from a hunch, unfalsifiable criteria, invented labels). The only trimmable content is a small amount of motivational framing in the opening.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and imperative with commands doing the talking, but a few rhetorical flourishes ('An issue is maintainer evidence, not a sticky note', 'Vague issues become queue noise; concrete ones become fixes with credit') could be trimmed — efficient with minor over-explanation rather than lean throughout. | 4 / 5 |
Actionability | Every step carries executable commands (gh issue list/pr list with --search, gh label list, gh api milestones, and a complete gh issue create invocation with --label/--milestone/--body-file flags) plus concrete title and acceptance-criteria examples, leaving only trivial live-value substitution to the reader. | 5 / 5 |
Workflow Clarity | Seven well-sequenced steps include explicit validation gates: confirm the code claim from source rather than memory (step 1), a pre-file duplicate/PR search (step 2), and a readiness gate ('If you cannot state how it's verified, the issue is not ready') backed by the Red flags checklist. Filing a single issue is neither destructive nor batch, so no validation cap applies. | 5 / 5 |
Progressive Disclosure | This is a single-purpose, single-file skill with well-organized sections (When to use, Workflow, Red flags, Output) and nothing that belongs in a separate file — labels and milestones are deliberately read from the live set rather than inlined as a static reference, so no external bundle is needed. | 5 / 5 |
Total | 19 / 20 Passed |