Conciseness

The body is short and sectioned, with the Quick Reference bullets and Check/Fix/Explain/Code Review sections carrying real information. The one padded spot is the opening sentence "Search engines may not discover all your pages through links alone—a sitemap ensures every important page gets indexed", which explains a concept Claude already knows; trimming it would reach the lean anchor at 5.

Actionability

Some concrete guidance exists — "a valid XML sitemap accessible at /sitemap.xml" and "proper priority and changefreq values" give specific targets — but there are no executable commands or code in the body (e.g. how to fetch/validate the sitemap, curl the URL, check the XML against the sitemap schema), and "properly formatted" is undefined here. This matches the 'some concrete guidance but incomplete' anchor rather than the mostly-executable anchor at 4.

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a recognizable sequence, but there are no validation checkpoints: nothing says how to confirm the sitemap is valid or how to verify the fix took effect (e.g. re-fetch /sitemap.xml, validate XML, check the HTTP response). The operations are not destructive/batch so the hard cap at 3 doesn't force this score, but the missing checkpoints place it at the 'steps listed but validation gaps' anchor rather than 4.

Progressive Disclosure

The body is a lean overview with clear sections and a well-signaled, one-level-deep pointer — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and the referenced file exists and contains the expected detail (code example, why-it-matters). Minor organization gaps keep it below 5: the pointer is plain text rather than a link, the rule-page URL is duplicated from the frontmatter as a trailing bare line, and the closing '---' separator serves no structural purpose.

Specificity

The description names the domain ("auditing metadata, crawlability, structured data, or indexability") and gives one concrete action ("Verify the rendered HTML and HTTP response rather than relying only on source files"), matching the 'names domain and 1-2 concrete actions' anchor. It does not list several specific actions (generate, validate, submit a sitemap), so it falls short of 4.

Completeness

The 'when' is explicit ("Use when auditing metadata, crawlability, structured data, or indexability"), but the 'what' is thin: the only capability stated is "Verify the rendered HTML and HTTP response rather than relying only on source files", which reads as a caveat rather than a clear statement of what the skill does (create, validate, and submit an XML sitemap). This sits between the vague-'what' anchors and the both-present anchor at 4.

Trigger Term Quality

Natural SEO keywords are present — "auditing", "metadata", "crawlability", "structured data", "indexability", "XML sitemap" — which users auditing a site would plausibly say. Common variations like "SEO", "search engines", "Google Search Console", or "sitemap.xml" are missing, so it does not reach comprehensive coverage at 5.

Distinctiveness Conflict Risk

The sitemap niche is somewhat distinct, but the trigger terms "auditing metadata", "structured data", and "indexability" are shared with sibling SEO skills (meta-tag rules, structured-data rules), creating real overlap risk with closely related skills in the same category. It is more targeted than a generic 'helps with documents', yet not the clear-niche, minimal-conflict case at 5.