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.
A dense, well-structured body with executable scaffolding code and a real reference bundle, scoring solidly across all dimensions. Main gaps: the inline capability table and duplicated reference list cost tokens, the declaration format lacks a code example, and testing guidance has no explicit feedback loop.
Suggestions
Deduplicate the reference links: the 'Declare access' section links and the 'References' section list the same five files; keep one canonical list and drop the other.
Move the 28-row capability table to a dedicated reference (e.g. alongside sandbox-boundaries.md) and inline only the few capabilities needed to follow the scaffold example, keeping the always-loaded SKILL.md lean.
Add a short emdash-plugin.jsonc example under 'Declare access' and an explicit validate-fix-retry loop in the testing section (e.g. 'if Block Kit validation fails, fix the page payload and re-run the runtime host').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Prose is uniformly lean and imperative ('Sandboxed runtime code can use Web APIs but not Node.js built-ins') with no explanation of known concepts, but the 28-row capability table and the duplicated reference link list (inline links at 'Declare access' repeated in the 'References' section) are trim candidates. | 4 / 5 |
Actionability | The scaffold commands ('pnpm dlx @emdash-cms/plugin-cli init my-plugin') and the complete src/plugin.ts example are copy-paste ready, but the central 'Declare access' step gives no example of the emdash-plugin.jsonc declaration format it pivots on. | 4 / 5 |
Workflow Clarity | Section order follows the natural build flow (choose format → scaffold → declare access → routes/hooks/UI → test) and verification exists (two test-host functions, 'Dispose every host after use', pnpm run test), but there is no explicit validate-fix-retry loop and the sequence is implicit rather than signposted. | 4 / 5 |
Progressive Disclosure | Twelve one-level-deep references, all real files, linked per-topic ('Read the focused reference for the API being used') and again in a References section; however the reference list is duplicated and the reference-grade capability table is inlined in the overview. | 4 / 5 |
Total | 16 / 20 Passed |