Content
86%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 tightly written, highly actionable skill body with executable gh/git commands, a gated workflow, and clean sectioning. The only real weakness is minor motivational padding in the opening paragraph.
Suggestions
Trim the rhetorical framing in the intro paragraph ("maintainer evidence, not a sticky note… queue noise… fixes with credit") to a single concrete quality statement.
Consider an explicit pre-file self-check step that re-runs the acceptance criteria as a gate, which would add the validate→retry feedback loop the top workflow_clarity anchor expects.
Add one or two natural trigger synonyms (e.g. "report a bug", "track an issue") to broaden keyword coverage in the description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely lean and assumes Claude's competence, but the intro carries light rhetorical padding ("maintainer evidence, not a sticky note", "queue noise", "fixes with credit") that could be trimmed without losing guidance. | 4 / 5 |
Actionability | Provides fully executable, copy-paste-ready commands throughout (git rev-parse, grep, gh issue/pr/label list, gh api milestones, and a concrete gh issue create example) covering the common filing cases. | 5 / 5 |
Workflow Clarity | A clear 7-step sequence with explicit gates (confirm claims from source, dedup search, "if you cannot state how it's verified, the issue is not ready") plus a red-flags checklist, but it lacks a true validate→fix→retry feedback loop, which is appropriate for a one-shot file yet keeps it below the top anchor. | 4 / 5 |
Progressive Disclosure | Well-organized into clearly signaled sections (When to use, Workflow, Red flags, Output) with no content that belongs in a separate file and no nested or buried references; the self-contained structure navigates easily. | 5 / 5 |
Total | 18 / 20 Passed |