Conciseness

Every sentence carries non-obvious, repo-specific facts ("Import from `src/lib` as `#lib/...`... SvelteKit 3 has no `$lib`", "`svelte-check` needs the `typescript` package, which this repository does not depend on", the `./$types` CI failure mode) with zero padding and no explanation of concepts Claude already knows — matching anchor 5's 'every token earns its place' rather than anchor 4's 'minor instances of over-explanation'.

Actionability

Commands are copy-paste ready with exact flags: `bunx @sveltejs/mcp get-documentation 'svelte/$state,kit/$app-paths'`, `svelte-autofixer src/lib/components/Entry.svelte --svelte-version 5.57.3`, `env -u NODE_PATH bun run typecheck`, plus concrete code patterns (`class={["base", flag && "extra", className]}`, `renderComponent` from `test/support/render.ts`) — matching anchor 5's fully executable guidance covering the common cases.

Workflow Clarity

The 'Look it up' section gives an ordered sequence (list-sections → get-documentation → autofixer → check:svelte) with an explicit feedback loop ("Repeat until it reports nothing") and explicit validation (`bun run check:svelte`, `fmt:check`), matching anchor 5's 'explicit validation steps; feedback loops' rather than anchor 4, whose 'minor validation gaps' are absent here.

Progressive Disclosure

No bundle files exist and none are needed: the ~70-line body is organized into five clear, scannable sections (Look it up, Checks, Conventions, Tests, Route types) with no inlined content that belongs in a separate file, and the one cross-skill pointer ("Follow the `bdd-bun-test` skill") is clearly signaled — matching anchor 5's clear, easy-to-navigate structure.

Specificity

Quotes like "looking up the official documentation", "checking components with the official autofixer and svelte-check" are concrete, tool-named actions, but "the runes conventions the code follows, and how components are tested" are topic nouns rather than actions — matching the 'several specific actions with minor gaps' anchor (4), not the fully action-based comprehensive coverage of anchor 5.

Completeness

The 'what' is explicit (documentation lookup, autofixer/svelte-check verification, runes conventions, testing approach) and the 'when' is explicit with concrete triggers ("Use when writing or changing .svelte files, routes, vite.config.ts, hooks or the prerender setup"), exactly matching anchor 5's clear and explicit what+when with trigger phrases; anchor 4's 'when could be more specific' does not apply.

Trigger Term Quality

The trigger clause covers ".svelte files, routes, vite.config.ts, hooks or the prerender setup, or when a Svelte or SvelteKit API is in doubt" — natural user phrasing including file extensions and synonyms, matching the comprehensive coverage anchor (5) better than anchor 4's 'a few natural terms missing'.

Distinctiveness Conflict Risk

"Svelte 5 and SvelteKit 3 in this repository" plus Svelte-specific triggers (.svelte, runes, prerender, SvelteKit API) carve out a clear niche with minimal overlap risk against generic web/JS skills, matching anchor 5 rather than anchor 4's 'minor overlap risk with closely related skills'.