Content
65%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 terse, executable CLI command reference with concrete examples for every subcommand, weakened by duplicated config sections, a truncated description, absent flag semantics, and no workflow sequencing or validation guidance for multi-step operations like setup and config set. Organization is adequate but the entire reference is inlined with no progressive disclosure structure.
Suggestions
Deduplicate the repeated 'config get'/'config set'/'config list' sections and complete the truncated 'config opencode' description ('Generate OpenCode config (alias for' ends mid-sentence).
Add a short usage workflow that sequences the commands (e.g., 'omniroute setup' -> 'config list' -> 'config get <tool>' -> 'config set <tool> --model <model>' -> 'config validate <tool>') with a validation checkpoint before writing config.
Show at least one flag in action per complex subcommand (e.g., 'omniroute setup --add-provider --provider <id> --api-key <value>') and briefly annotate what key flags like '--tray' or '--allow-container-write' do.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean flag/example catalog with no concept explanations or padding, but the Overview repeats the description verbatim, the 'config get'/'config set'/'config list' subcommands each appear twice with conflicting flags, and 'config opencode' has a truncated description ('Generate OpenCode config (alias for'), all of which waste tokens. | 4 / 5 |
Actionability | Every subcommand has a copy-paste-ready example command and a flag list, meeting the 'mostly executable' anchor. It falls short of 5 because flags lack descriptions, no example demonstrates flag usage (e.g., 'setup' shows a bare 'omniroute setup' despite ten flags), and placeholder values like '<tool>' are never instantiated. | 4 / 5 |
Workflow Clarity | The content is a flat command catalog with no sequenced guidance for multi-step tasks (e.g., config list -> config get <tool> -> config set -> config validate), and validation exists only as an isolated command rather than a checkpoint. This is not a single-action simple skill, so the simple-skill exception does not apply. | 3 / 5 |
Progressive Disclosure | Per-subcommand headers and a Quick install section give reasonable structure, but a ~280-line full command reference is inlined in SKILL.md with no bundle files, and duplicated config sections signal weak organization — matching 'some structure but could be better organized'. | 3 / 5 |
Total | 14 / 20 Passed |