Content
75%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.
The body is dense, actionable, and well-sequenced with strong routing and bounded verification. Its main defect is progressive disclosure: it leans heavily on a `reference/` directory of markdown files that is not present, so much of its promised navigation resolves to broken links.
Suggestions
Ship the `reference/` markdown files the body points to, or rewrite the routing to depend only on bundle files that actually exist.
Trim the rhetorical opening framing ("out-of-distribution craft", "award-winning design director") to tighten conciseness without losing the directive tone.
Make the verification workflow's validation checkpoint fully explicit (a concrete command or checklist) to lift workflow clarity to the top anchor.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean and opinionated with little concept-over-explanation, but the opening framing ("award-winning design director with impeccable understanding", "out-of-distribution craft") and a few rhetorical flourishes add mild padding. | 4 / 5 |
Actionability | Concrete executable commands ("node <skill-base-dir>/scripts/context.mjs", "--target <path>"), a full command/route table, and precise routing rules give fully actionable, copy-ready guidance. | 5 / 5 |
Workflow Clarity | Clear Setup sequence and bounded verification ("inspect once with a batched round... confirm with at most one more round, and stop polishing") provide good checkpoints; minor gaps keep it just short of fully explicit validation loops. | 4 / 5 |
Progressive Disclosure | The body is well sectioned but references ~25 `reference/*.md` files (new-work.md, craft-floor.md, routing.md, critique.md, etc.) that are absent from this bundle — the `reference/` directory does not exist, so the navigation it signals is largely dead. | 2 / 5 |
Total | 15 / 20 Passed |