Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured router body: actionable CLI guidance, a deterministic ordered routing procedure with disambiguation checkpoints, and clean one-level-deep progressive disclosure to detail files and sub-skills. The main weakness is conciseness — routing precedence is repeated across the 'By task' and 'Pick a track' sections, inflating the token budget without adding new information.
Suggestions
Consolidate the precedence rules that appear in both 'By task' and 'Pick a track': state each rule once (e.g. 'peer signals take precedence over web rows', 'audit wins over the CLI check row') and reference it, rather than restating it inside multiple table cells and bullets.
Tighten the long routing-table cells: move the embedded caveats (peer-signal overrides, migration-before-docs ordering) into a short 'Precedence' note above the table so each cell stays a one-line signal-to-route mapping.
Consider collapsing 'By task' and 'Pick a track' into a single canonical decision procedure, keeping the task framing as a brief index that points into the signal table, to remove the overlapping guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body assumes Claude's intelligence (no concept explanations) and is information-dense, but precedence rules are restated across the 'By task' and 'Pick a track' sections — 'peer signals take precedence' and 'audit wins over the CLI check' each appear 2–3 times — and several table cells are paragraph-length, so it could be tightened. Not a 3 because of this redundancy; not a 1 because it is not padded with concepts Claude already knows. | 2 / 3 |
Actionability | Concrete, copy-paste-ready guidance: a CLI command table with 'When to reach for it' columns, explicit 'getstream skills <name>' install steps, a verbatim disambiguator question, and a verbatim navigation menu. For an instruction-only router the absence of code is appropriate and the guidance is fully actionable. | 3 / 3 |
Workflow Clarity | The routing procedure is explicit and ordered ('Scan the user's input for the signals below in order'), deterministic ('no probes, no fetches, no CLI checks at this stage'), with a clear disambiguation checkpoint ('ask one short question and wait') and an explicit install-then-invoke hand-off. No destructive batch operations require a validate-fix-retry loop here. | 3 / 3 |
Progressive Disclosure | The body is an overview that routes to clearly-signaled, one-level-deep references (RULES.md, peers.yaml, peers.schema.json, sendbird-data-migration.md) and to sub-skills, matching the 'clear overview with well-signaled one-level-deep references' anchor. Note: the referenced bundle files were not present in the review directory to verify on disk, but the disclosure structure as written is sound. | 3 / 3 |
Total | 11 / 12 Passed |