Dense, table-driven, and lean — directory/build and screenshot specs are tables, writing rules are terse bullets — with no explanation of concepts Claude already knows. It is not the level below because there is no padding or unnecessary rationale; even the brief justifications (e.g. why to use docs-svg-kit) earn their tokens.

Gives concrete executable guidance: 'turbo build --filter=editor && turbo start --filter=editor', 'pnpm --filter docs start', 'https://grida.co/_/<path>', 960x960 WebP q90, 'globalThis.grida' / 'WindowGlobalCurrentEditorProvider', and '?src=<url>', plus a copy-paste page-structure template. It is not the level below because commands and specs are specific and runnable, not pseudocode.

Sequences demo-state preparation as an explicit ordered fallback chain (fixture -> scripting API -> URL params -> manual) and provides a Pre-Publish Checklist with explicit verification checkpoints ('Page renders: pnpm --filter docs start', 'No broken links, no bare angle brackets'). It is not the level below because checkpoints are explicit, and the operations are not destructive/batch so no feedback loop is required to cap the score.

Single-file skill with no bundle, organized into clear sections (Directory & Build, Writing, Screenshots, Custom Graphics, Pre-Publish Checklist, Pitfalls) and well-signaled one-level-deep external resources ('See docs/AGENTS.md', 'use the docs-svg-kit skill'). It is not the level below because there is no monolithic wall of text and no nested/deep references.

Lists multiple concrete capabilities — 'Author and manage user-facing documentation', 'Covers writing style, tone, product screenshots, demo state preparation, and content structure' — matching the score-3 anchor for several specific concrete actions. It is not the level below because it goes well beyond naming a single domain and action.

Explicitly answers both 'what' (author/manage docs, writing style, screenshots, demo state, content structure) and 'when' via an explicit 'Use when creating or editing canvas editor documentation, capturing screenshots... or planning visual demos' clause. It is not the level below because the 'when' is explicit, not merely implied.

Provides natural trigger phrases users would actually say — 'write user docs', 'document this feature', 'screenshot for docs', 'canvas user guide', 'update help page' — with good coverage of common variations. It is not the level below because the terms are natural and varied rather than jargon or a single generic phrase.

Scoped to a clear niche — 'the Grida Canvas editor' and 'pages under docs/editor/' — with distinct triggers unlikely to fire for unrelated skills. It is not the level below because the domain binding is specific rather than a generic 'works with document files'.