Content
78%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-organized, mostly lean instruction-only skill with a clear sequenced workflow, concrete commands, and an appropriate single reference. The main weakness is repetitive restatement of the no-ingestion constraint, which slightly harms conciseness.
Suggestions
State the no-ingestion constraint once in the Constraints section and reference it from the workflow steps instead of restating it in the intro, 'What is covered', and steps 3–4, to reduce token redundancy.
Add an explicit error-recovery/feedback step (e.g., what to do when 'gh auth status' reports not authenticated) to lift workflow clarity from a checkpoint-only sequence to a full validate-and-retry loop.
Tighten the 'What is covered' and 'When to use' lists, which overlap the frontmatter description, to avoid duplicating trigger phrasing already present in the description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no concept over-explanation Claude would already know, but the no-ingestion constraint is restated across the intro, 'What is covered', Constraints, and Workflow steps 3–4 — minor tightening possible, so it sits above the midpoint rather than at the lean 5. | 4 / 5 |
Actionability | Concrete, executable guidance is present — 'gh --version', 'gh auth status', 'gh auth login', '--repo', and the '@014-agile-user-story' chain — with only minor gaps, fitting 'mostly executable guidance' rather than fully copy-paste-ready. | 4 / 5 |
Workflow Clarity | A clearly sequenced 5-step workflow with an explicit interactive-gate checkpoint ('stop, ask, wait'); it lacks an explicit error-recovery feedback loop, so it lands at 4 rather than the 5 anchor. | 4 / 5 |
Progressive Disclosure | The body is a concise overview with a single well-signaled one-level-deep reference to references/043-planning-github-issues.md (verified to exist), matching the 'clear overview with well-signaled one-level-deep references' anchor. | 5 / 5 |
Total | 17 / 20 Passed |