Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
An efficiently structured router skill that keeps the body lean and pushes detail into well-organized references. The only weakness is that the body itself contains no executable commands, relying entirely on delegation.
Suggestions
Add one inline example of the dispatch in action (e.g. "`gitter commit -m ...` → run the commit action") so the body is actionable without opening a reference.
Clarify how $REST is consumed by each action, since the body binds it but never explains its downstream use.
Surface a one-line guardrail in the body (e.g. confirm before committing on main/master) so safety behavior is visible before delegating to references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is ~10 lines with no padding or explanation of concepts Claude already knows; every token earns its place. | 3 / 3 |
Actionability | The dispatch logic (binding $ACTION/$REST, branching) is concrete, but the body delegates all executable commands to references with "follow its instructions," leaving the body itself without copy-paste-ready commands. | 2 / 3 |
Workflow Clarity | A clear three-step sequenced dispatch procedure with an explicit fallback ("Otherwise list the available actions"); appropriate for a simple routing skill. | 3 / 3 |
Progressive Disclosure | A lean overview pointing to two clearly-signaled, one-level-deep references ([commit](references/commit.md), [pr](references/pr.md)), both verified to exist, with easy navigation. | 3 / 3 |
Total | 11 / 12 Passed |