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.
A well-engineered router body: highly actionable, clean progressive disclosure into six real reference files, and clear workflow sequencing. The only meaningful deductions are minor redundancy (repeated SimReady exclusion and 150 GB teardown note) and validation checkpoints that live in referenced files rather than inline.
Suggestions
State the SimReady exclusion once (Purpose) and the 150 GB/teardown note once (Cross-skill teardown) instead of repeating each in Limitations/Hard Rules — this would tighten conciseness to a 5.
Add one line of inline validation guidance to the fetch workflow (e.g. what to do when `test -f` fails) so checkpoints don't depend entirely on referenced files.
Trim the 'When to Use' keyword list of near-duplicates (e.g. 'nurec', 'nurec router', 'nurec index') to reduce token cost without losing trigger coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and disciplined — terse tables, hard rules, and a troubleshooting matrix — and its concept explanations ("What is NuRec?" for NRE/USDZ/NCore V4/3DGUT) are product-specific knowledge Claude does not already have. Not a 5: there is noticeable redundancy — the SimReady exclusion is stated in Purpose, Hard Rules, and Limitations, and the 150 GB teardown note appears in both Limitations and the Cross-skill teardown section. | 4 / 5 |
Actionability | Fully executable guidance throughout: a copy-paste-ready clone/refresh block with env-var fallbacks and a `test -f` verification, executable secret-length check commands, a concrete 4-path local lookup order, a goal→skill picker table, and a troubleshooting table pairing exact error strings with solutions — covering the router's common cases end to end. | 5 / 5 |
Workflow Clarity | Clear sequencing (data → conversion → train → render → cleanup), an ordered local-lookup-then-upstream-clone procedure with an explicit verification step, and error-recovery feedback via the troubleshooting table. Not a 5: per-workflow validation checkpoints are deferred to the upstream sibling skills and references/workflows.md rather than stated inline, so checkpoints are present but not fully explicit. | 4 / 5 |
Progressive Disclosure | The body keeps the core routing content inline (picker tables, fetch recipe) while clearly signaling one-level-deep references — workflows.md, mix-ups.md, upstream-fetch.md, secrets-handling.md, teardown.md, maintenance.md — all of which exist in the bundle and none of which nest further. Navigation is easy and content is appropriately split. | 5 / 5 |
Total | 18 / 20 Passed |