The body is directive and assumes competence ('Do not hard-code the API surface', 'Show this as the first code block', 'No setup first') with no padding of basic concepts Claude already knows. The Bookstore Test metaphor is a load-bearing structuring device rather than decorative exposition, so tokens earn their place. Not a 2 because it lacks the editorializing filler of the anchor-2 example.

Provides concrete, executable guidance: exact file paths ('packages/sdk/src/index.ts'), a sourcing table, a fixed class ordering, and specific snippets to show ('project(id) → generate → getHtml', 'npm install @google/stitch-sdk'). For an instruction-only generator skill this is copy-paste-ready direction. Not a 2 because guidance is complete and specific, not pseudocode or abstract.

Clear sequence — source the API (table) → structure via Bookstore Test (Cover → Inner Flap → Reading the Book) → validate — with an explicit Validation checklist acting as verification checkpoints. README generation is not destructive/batch, so the missing-feedback-loop cap does not apply. Not a 2 because validation checkpoints are explicit, not implicit.

No bundle files are present and none are needed; the skill is a self-contained single file with well-organized sections (headings, tables, checklist) and no nested references. Per the simple-skill note, well-organized single-file content with no external-reference need scores 3. Not a 2 because it is cohesive and navigable rather than a monolithic wall or a split candidate with missing signals.

Quotes 'Generate or update the README', 'Use the Bookstore Test structure', and 'source the current API from the codebase' — three concrete actions, matching the anchor for listing multiple specific actions. Not a 2 because it goes beyond naming a domain to enumerating concrete operations.

Explicitly states what ('Generate or update the README for the Stitch SDK') and when ('Use when the README needs to be written or updated'), matching the anchor for clearly answering both with an explicit 'Use when' clause. Not a 2 because the 'Use when' trigger is present, not implied.

The only trigger phrase is 'Use when the README needs to be written or updated' — a single condition missing common natural variations a user would say (e.g. 'docs', 'document my SDK', 'write a readme'). Not a 3 because keyword coverage is narrow, not a 1 because 'README' is a genuine natural term.

Tied to a specific product ('Stitch SDK') and a named strategy ('Bookstore Test'), giving it a clear niche unlikely to trigger for unrelated skills. Not a 2 because the SDK-specific framing and distinct structural marker narrow the conflict surface.