Content
86%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 router skill body: concise, points to a version-matched source of truth, and cleanly defers detail to bundled docs and one reference file. Its only limitation is inherent to the router pattern — it offers navigation rather than executable eve examples, which slightly caps actionability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence: it states the source of truth, the entry path (node_modules/eve/docs/README.md), and the install/scaffold fallback, with no padding or explanation of concepts Claude already knows. | 5 / 5 |
Actionability | It gives concrete, executable commands (npm install eve, npx eve init <agent-name>) and a specific path to read, but the primary instruction ('read the bundled docs') is a pointer to external material rather than copy-paste-ready working code, leaving a small gap versus fully executable guidance. | 4 / 5 |
Workflow Clarity | There is a clear sequence: read bundled docs first, install/scaffold if eve is missing, then read the relevant guide before writing code, plus a handoff boundary reference. It lacks an explicit validation/feedback checkpoint, but this routing skill does not perform destructive or batch operations, so the destructive-cap does not apply. | 4 / 5 |
Progressive Disclosure | The body is an overview router that points one level deep to the bundled docs and to references/source-of-truth.md (a real file), with clearly signaled navigation and no inline bulk content that belongs elsewhere. | 5 / 5 |
Total | 18 / 20 Passed |