Content
75%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.
The body is an actionable, well-sequenced read-only workflow with concrete gh commands throughout. It is efficient and well-organized, with minor gaps in section c concreteness and no validation checkpoints (not required for read-only analysis).
Suggestions
Provide a concrete gh api command or jq filter for the 'recently stale issues' case in section c instead of prose guidance.
Tighten the classification table and prose to remove cues that repeat across steps 2 and 3.
Consider splitting the per-issue analysis output template into a reference file if the skill grows further.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean with concrete gh commands, tables, and tight bullets, but includes a few trimmable prose passages (section 2c and some repeated classification cues). | 4 / 5 |
Actionability | Provides copy-paste-ready gh api and gh issue view commands with --jq filters covering the main query patterns, though section c ('recently stale') lacks a concrete executable command. | 4 / 5 |
Workflow Clarity | A clear 5-step sequence (gather, deep-dive, classify, prioritize, output) with good structure; read-only so the destructive/batch validation cap does not apply, but no explicit validation checkpoints are present. | 4 / 5 |
Progressive Disclosure | A single self-contained file with well-organized sections and no nested or dead references; slightly long for one file but cohesive and appropriately structured with no bundle files needed. | 4 / 5 |
Total | 16 / 20 Passed |