The body is lean and assumes Claude's competence — it gives specific layout and copy guidance without explaining what a dashboard or bar chart is. It is not a 2 because there is no padded conceptual explanation to tighten.

Guidance is concrete and copy-paste-ready: pixel widths ('220–260px sidebar'), CSS ('font-feature-settings: \'tnum\''), '~30 bars', data-od-id attributes, and an exact artifact format. It is not a 2 because the instructions are executable specifics, not pseudocode or abstract direction.

A clear 5-step sequence (read DESIGN.md, pick voice, layout, write HTML, self-check) ends with an explicit validation checklist. It is not a 2 because the self-check supplies the checkpoint that the anchor-2 example lacks, and the task is non-destructive so no retry loop is required.

No bundle files exist, and the self-contained body is organized into clear sections (Workflow, Output contract) with the only external doc (DESIGN.md) injected rather than nested. It is not a 2 because content is appropriately organized with no monolithic wall of text or multi-level references.

The description lists multiple concrete components — 'left rail navigation, ticker bar of community signals, headline KPIs, a 30-day mutual-matches bar chart, and a match-rate trend block' — rather than vague language, matching the multi-action anchor. It is not a 2 because the action set is comprehensive and specific, not partial.

It answers both what ('A consumer-feeling dating / matchmaking dashboard ...') and when via an explicit 'Use when the brief asks for ...' clause, in third person. It is not a 2 because the when-guidance is explicit, not merely implied.

It surfaces natural user phrasing — 'dating site', 'matchmaking', 'community dashboard', 'social network dashboard' — giving good coverage of terms a user would actually say. It is not a 2 because it lists several common variations rather than a single keyword.

The dating/matchmaking consumer-dashboard niche with its distinct triggers is unlikely to fire for unrelated skills. It is not a 2 because the niche and triggers are specific enough to avoid overlap with generic dashboard or document skills.