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 a well-organized, high-signal map of the extension authoring surface with executable examples, a ranked verification workflow, and clear navigation to source-of-truth files. Its main gaps are the absence of bundle files to offload reference-grade detail and slightly less explicit validation loops for destructive paths.
Suggestions
Add a references/ file (e.g. API.md) for the 'What handlers receive' ctx field inventory and 'Rules that bite' list so SKILL.md stays a lean overview, then link to it from the touchpoint table.
Wrap the `ctx.workspace` write guidance in an explicit validate-checkpoint (check `canWriteDocument` → write → confirm `{ ok }` → else handle `reason`) so destructive operations get the missing feedback loop.
Add one inline copy-paste snippet per common touchpoint (e.g. a minimal `registerPane` example) alongside the table so the most frequent cases are fully executable without opening the external docs.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and almost entirely non-obvious domain knowledge (id rules, trust gating, lifetime semantics, the second-React bug), with little padding of concepts Claude already knows. It earns a 4 rather than 5 because sections like 'Where extensions live' and the examples catalog are information-rich but could be tightened, and a few sentences restate constraints already implied by the table. | 4 / 5 |
Actionability | Provides executable code (the hello factory), concrete commands (`bun run typecheck`, `hunk --extension ./my-ext.ts my-command sync --help`), and a precise API lookup table mapping intent to call. Not a 5 because most guidance is a map to external sources rather than inline copy-paste snippets for each common case. | 4 / 5 |
Workflow Clarity | The 'Verifying' section is an ordered, cost-ranked checklist with explicit checkpoints, and 'If it does not load' gives a feedback loop for triage. It stops at 4 because the build path lacks an explicit validate-then-retry loop for the typecheck/JSX-config steps, and the destructive-workspace-write rules are stated but not wrapped in a verify checkpoint. | 4 / 5 |
Progressive Disclosure | Structure is good: a touchpoint table plus a 'Sources of truth — read before writing' table that signals one-level-deep references (docs/extensions.md, types.ts, examples/) for detail. No bundle files exist in references/scripts/assets to offload the API reference, so some reference-grade content is inlined; it stays at 4 rather than 5 because the inlined 'What handlers receive' and 'Rules that bite' blocks read like reference material that a separate file could hold. | 4 / 5 |
Total | 16 / 20 Passed |