Conciseness

Every line is a dense gotcha or instruction ("Astro v5+ defines collections in `src/content.config.ts` (not `src/content/config.ts`)", the client:* ladder with one-word cost labels), assuming Claude's competence and adding only framework-specific knowledge — matching anchor 5. Version references state current truth with the old pattern negated inline rather than using date-conditional guidance, so the time-sensitivity penalty does not apply.

Actionability

Concrete guidance throughout — file paths (`src/pages/api/*.ts`, `astro.config.mjs`), a runnable command (`astro add react tailwind mdx sitemap`), and a near-complete `glob({ pattern: '**/*.{md,mdx}', base: './src/content/blog' })` loader example — matching anchor 4. Not 5 because there is no complete copy-paste code block for defining a collection or calling `getCollection`; not 3 because the guidance is executable and specific, not pseudocode.

Workflow Clarity

"Add a collection" is a clear 4-step sequence with an explicit validation checkpoint ("The build must exit zero"), matching anchor 4. Not 5 because no fix-and-retry feedback loop is described; not 3 because the sequence is present with a checkpoint, and the destructive/batch cap does not apply to this non-destructive workflow.

Progressive Disclosure

The body is under 50 lines, organized into clear sections (Gotchas, Layout, Add a collection, integrations), and no bundle files exist or are needed at this size — matching the rubric's simple-skill exception where well-organized sections alone score 5. Content is appropriately inlined rather than split into reference files.

Specificity

"Astro pages, layouts, content collections, hydration directives and integrations" lists several concrete capability areas, matching anchor 4 (several specific items, minor gaps). Not 5 because the list is verbless domain objects rather than actions, leaving minor coverage gaps in what is done with them; not 3 because five concrete areas clearly exceed the '1-2 concrete actions' anchor.

Completeness

Both parts are explicitly stated: the what names concrete capability areas, and the when — "Use when adding or changing Astro pages, components or content collections, or choosing a client: directive" — is more explicit and specific than anchor 4's example ("Use when working with PDF files"), matching anchor 5's clear what-and-when with concrete trigger phrases.

Trigger Term Quality

"adding or changing Astro pages, components or content collections, or choosing a client: directive" contains natural phrases a user would actually say, matching anchor 4 (good keyword coverage, a few natural terms missing). Not 5 because synonyms and file extensions (e.g., routes, islands, .astro) are absent; not 3 because the terms are specific and natural rather than generic.

Distinctiveness Conflict Risk

"Astro", "content collections", "client: directive" and "hydration directives" form a clear niche with distinct triggers and minimal conflict risk, matching anchor 5. The only generic term is "components", but it is scoped to the Astro context; not 4 because the trigger set is framework-specific and unlikely to fire a wrong skill.