Conciseness

The body is dense and purposeful with no explanations of concepts Claude already knows (e.g., "never `next build` here — it would corrupt a running dev server's `.next/` directory"); minor redundancy — the workflow link repeated in Instructions and Resources, and the Error Handling table overlapping the reference's Troubleshooting — keeps it below anchor 5's every-token-earns-its-place.

Actionability

Concrete commands and paths appear throughout ("perl -pi, escaping /, \, and &", "npm run i18n:check and npx tsc --noEmit", "lib/datasets.ts", "next.config.js"); it falls short of anchor 5 because the fully executable workflow and the actual perl substitution command are delegated to the remote canonical doc rather than given inline.

Workflow Clarity

An 11-step numbered sequence with explicit validation (step 10: "Verify with npm run i18n:check and npx tsc --noEmit"), feedback loops ("Print the log and fix before reporting success — never report success with a failing type check"), a symptom/cause/fix error table, and a confirmation gate before overwriting a destination — matching anchor 5's explicit validation steps with error recovery.

Progressive Disclosure

The bundle reference references/reference.md is real, one level deep, and clearly signaled ("Template and token reference"); it is not 5 because the primary executable workflow is delegated to an external URL rather than a bundled file, and the Error Handling table partially duplicates the reference's Troubleshooting section, leaving minor organization gaps.

Specificity

"Scaffold a new PortalJS data portal from a brief", "Copies the canonical template from examples/portaljs-catalog", and "substitutes project tokens" are three concrete actions, matching anchor 4; it is not 5 because the interview, UI language setup, dataset seeding, and verification steps in the body are omitted (more than minor gaps), and not 3 because it goes beyond the 1-2 actions of that anchor.

Completeness

Both are explicit: the what ("Scaffold a new PortalJS data portal... Copies the canonical template... substitutes project tokens") and the when ("Use when starting a brand-new data portal project from scratch"). The single when-clause is less specific than anchor 5's multiple concrete trigger phrases, but well above anchor 3 where when is missing or implied.

Trigger Term Quality

Natural terms like "new PortalJS data portal", "data portal", and "project from scratch" cover what a user would say, but common variants such as "create", "build", or "set up a portal" are missing, so it fits anchor 4 rather than anchor 5's comprehensive synonym coverage.

Distinctiveness Conflict Risk

The PortalJS scaffolding niche ("Scaffold a new PortalJS data portal") with its distinct new-project trigger ("starting a brand-new data portal project from scratch") has minimal overlap risk with sibling skills like portaljs-add-dataset or portaljs-add-chart, matching anchor 5's clear niche with distinct triggers.