The body is dense and assumes Claude's competence — it never explains what Hugo, geekdoc, or YAML are, and every line carries a specific fact (paths, schemas, FROZEN CSS, divergence). It is not level 2 because there is no unnecessary explanation or padding to tighten.

It provides concrete executable commands ('grep -n '"<icon-value>"' docs-site/layouts/partials/menu.html', 'cd docs-site && hugo --minify --gc') plus copy-paste-ready YAML menu and vercel.json redirect examples. It is not level 2 because the guidance is complete and executable rather than pseudocode with missing details.

Workflows carry explicit validation checkpoints: the icon-edit flow ('grep ... If absent, add the SVG path case') and the build check ('hugo --minify --gc must complete warning-free') with a feedback loop noting malformed _meta.yaml/menu entries surface there. It is not level 2 because validation is explicit rather than implicit or missing.

The body is well-organized into clear sections (path map, entry schema, icon coupling, redirect pattern, divergence, tooling) with one-level-deep, clearly signaled external references (Skill("hns-oss-docs-verify"), the report path) and no nested reference chains. It is not level 2 because references are clearly signaled and appropriately split rather than inline or poorly organized.

The description enumerates many concrete objects — 'exact paths and schemas for hugo.toml, per-locale content/<locale>/_meta.yaml, data/menu/main.yaml ... layouts/partials/menu.html, shortcodes, the FROZEN moai-brand.css, vercel.json redirect examples' — listing multiple specific concrete surfaces rather than vague language. It is not level 2 because coverage is comprehensive across named files rather than naming only a domain and a few actions.

It answers 'what' ('docs-site structure map ... exact paths and schemas') and 'when' with an explicit equivalent trigger clause ('Loaded by the structure-curator before any navigation or config edit'). The explicit trigger guidance prevents the level-2 cap; it is not level 2 because both what and when are present and explicit.

Terms like 'oss-docs harness structure-curator', 'icon-to-SVG-case coupling', and 'design-vs-guides divergence' are internal jargon a user would rarely say naturally, though 'paths and schemas', 'navigation', and 'config edit' are somewhat relevant. It is not level 3 because it lacks common natural variations users would actually say, and not level 1 because it does include some concrete relevant keywords.

The niche is highly specific — this particular Hugo geekdoc docs-site harness with FROZEN moai-brand.css and vercel.json redirects — making it unlikely to trigger for the wrong skill. It is not level 2 because the triggers are distinct rather than merely 'somewhat specific'.