Conciseness

Every paragraph carries non-obvious, skill-specific constraints ("Top must equal bottom and left must equal right, within 4px", "text drawn with dominant-baseline='central' has its visual top about 0.35 × size above its y", "Published files are a mix of 1x and 2x; that is history, not a target") with zero padding and no explanation of concepts Claude already knows. This matches anchor 5 — every token earns its place.

Actionability

Fully executable, copy-paste-ready guidance throughout: the grep/curl reference-fetching commands, a near-complete diagram module template with exact field semantics, `./render.sh`, `CHROME=/path/to/chrome ./render.sh`, `node gen.mjs <name>`, `python3 scripts/measure.py light/<name>.png`, and exact primitive signatures like `browserWindow(t, x, y, w, h, url, body = '')`. This matches the anchor-5 exemplar of copy-paste commands covering the common cases.

Workflow Clarity

Six numbered steps (read mdx → pull references → write module → render → review → hand off) with an explicit validation checkpoint and feedback loop: "Look at both PNGs at full size, against review-checklist.md and against the references... Run python3 scripts/measure.py... Fix in constants and re-render. Do not hand off a PNG you have not looked at." The hand-off step adds its own verification (srcLight basename must match the PNG name). This is a non-destructive skill, so the batch/destructive cap does not apply.

Progressive Disclosure

The task→file table is well-designed and references are one level deep and clearly signaled, but scored against the actual bundle, two of the six referenced paths (`style-tokens.md` and `review-checklist.md`, cited three times in the body and both load-bearing for the color conventions and the review step) do not exist in the bundle. Dead navigation targets for core reference material are more than the 'minor organization gaps' of anchor 4, though the structure itself is far better organized than anchor 3's exemplar.

Specificity

"Draw diagrams for the Next.js docs", "Hand-written SVG from a primitives library, rendered by headless Chrome at 2x", and "No AI image generation" name several concrete, specific actions for a well-defined deliverable (light/dark PNGs matching the published Image-tag convention). It sits at anchor 4 rather than 5 because it describes one task with a detailed method rather than the multiple distinct actions of the anchor-5 exemplar, and above anchor 3 because coverage is thorough, not 1-2 actions.

Completeness

It explicitly answers both questions: what ("Draw diagrams for the Next.js docs in the style of the ones already published there... Hand-written SVG from a primitives library, rendered by headless Chrome at 2x") and when ("Use when a guide or API reference needs a new diagram or an existing one needs a change"). The when-clause carries concrete trigger phrases, matching the anchor-5 exemplar pattern; anchor 4 would require the when to be less explicit than it is.

Trigger Term Quality

Natural trigger terms are well covered: "diagram", "new diagram", "Next.js docs", "guide", "API reference", "image", and "an existing one needs a change". It falls short of anchor 5's comprehensive synonym coverage (e.g., "figure", "illustration", "chart" are absent) but clearly exceeds anchor 3's partial coverage.

Distinctiveness Conflict Risk

The Next.js docs niche is pinned by the mdx `<Image srcLight="/docs/light/<name>.png" srcDark="/docs/dark/<name>.png">` convention, and "No AI image generation" explicitly separates it from image-generation skills. Clear niche with distinct triggers and minimal conflict risk, matching anchor 5.