Content
85%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-organized, actionable router with strong progressive disclosure and clear workflow sequencing; its main weakness is minor repetition across sections that slightly hurts token efficiency.
Suggestions
Consolidate the SimReady exclusion so it lives in one canonical place (e.g., the Limitations section) and is referenced rather than restated in Purpose and Hard Rules.
Avoid restating the full prerequisite list in the body since the frontmatter compatibility field already captures it; link to it instead.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and well-structured, but there is repetition that could be tightened: the SimReady caveat appears in Purpose, Hard Rules, and Limitations, and the Prerequisites section duplicates the frontmatter compatibility block. | 2 / 3 |
Actionability | Provides copy-paste executable bash (the upstream clone/refresh block, secret-verification checks) and a concrete goal-to-skill picker table with explicit ordering arrows — fully actionable routing guidance. | 3 / 3 |
Workflow Clarity | Multi-step NuRec workflows are explicitly sequenced (data -> conversion -> train -> render -> cleanup) with ordering arrows in the picker table, and the fetch recipe includes an explicit validation checkpoint (`test -f .../SKILL.md`) plus a 'read upstream before mutating' rule. | 3 / 3 |
Progressive Disclosure | Clear overview body with well-signaled, one-level-deep references to real bundle files (workflows.md, mix-ups.md, teardown.md, upstream-fetch.md, secrets-handling.md, maintenance.md), all of which exist in ./references/; content is appropriately split for easy navigation. | 3 / 3 |
Total | 11 / 12 Passed |