Content
82%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.
An exemplary routing-style SKILL.md: lean, well-organized, with a clear task-to-reference table and all reference files present. The main defects are dangling bundle references (missing `templates/` and `.agents/` paths) and the absence of fallback guidance for tasks that match no routing row.
Suggestions
Fix the dangling references: four routing rows cite `templates/*.yaml` and one cites `.agents/knowledge/veomni-seed-omni.md`, but neither exists in the skill bundle — add the template files or correct the paths so navigation never dead-ends.
Add a fallback instruction for tasks that match multiple routing rows or none (e.g., 'if no row matches or several do, start with `references/source-of-truth.md`') to close the workflow-clarity gap.
State in one line at the top what the skill itself does (routes SeedOmni tasks to the references and pins hard constraints), which would also strengthen the description's generic 'development guidance' framing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~60-line body is lean with zero padding: no general-knowledge explanations, terse factual baseline bullets ("Training graphs are flat edge lists over `module[.method]` endpoints"), and every section (First Checks, Routing, Baseline, Templates, Siblings) earns its tokens. This matches anchor 5 ('assumes Claude's competence; every token earns its place') rather than anchor 4, which requires identifiable over-explanation to trim — there is none. | 5 / 5 |
Actionability | As an instruction-only routing skill it gives concrete, executable guidance: a task→file routing table with exact paths, named live modules to use as implementation maps ("live `fake_model`, Janus, and Qwen modules"), and a validation routing row. However, four routing rows point to `templates/*.yaml` files and one to `.agents/knowledge/veomni-seed-omni.md`, none of which exist in the bundle, so following them dead-ends — a minor gap that fits anchor 4 ('mostly executable guidance... minor gaps') rather than anchor 5. | 4 / 5 |
Workflow Clarity | The sequence is clear: confirm the task touches SeedOmni (with concrete check paths), treat live code as source of truth, pick the smallest reference set from the table, and a dedicated validation row routes risky verification. It falls short of anchor 5 because there are no explicit checkpoints for edge cases — nothing says what to do when a task matches multiple rows or none, or when to re-check after reading a reference — matching anchor 4's 'clear sequence with most checkpoints present; minor validation gaps'. | 4 / 5 |
Progressive Disclosure | The structure itself is exemplary: a pure overview entrypoint with a well-signaled routing table and seven one-level-deep reference files, all of which exist in `references/`. Scored against the actual bundle, though, the `templates/` directory referenced by four routing rows and `.agents/knowledge/veomni-seed-omni.md` are missing, leaving dangling navigation paths — a minor organization gap that fits anchor 4 rather than anchor 5's 'easy navigation'. | 4 / 5 |
Total | 17 / 20 Passed |