Conciseness

The body is short overall, but the reduced-click-through point is repeated three times (intro paragraph, Quick Reference bullet, and the Explain section), and the Explain section restates what the nosnippet directive does — a concept the skill's own reference file already covers and Claude largely knows. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not level 2 because there is no multi-sentence padding of basic concepts and the actionable sections are lean.

Actionability

Concrete, executable guidance throughout: 'Flag any that contain nosnippet or max-snippet:0', 'Remove nosnippet from the <meta name=robots> content attribute', 'Replace with max-snippet:-1', and both the meta tag and X-Robots-Tag locations are named. As an instruction-only skill, absent inline code is acceptable, but no example of the tag markup appears in the body itself (only in rule.md), leaving a minor gap versus fully copy-paste-ready level 5.

Workflow Clarity

The Check → Fix → Code Review sections give a recognizable sequence with one checkpoint ('Confirm these pages intentionally suppress snippets'), but the audit is a batch operation over 'each important page' and there is no post-fix verification step (e.g., re-check the tag or confirm via Search Console after removal) and no explicit step ordering. Per the guideline capping batch operations without validation at 3, and matching 'sequence present but checkpoints missing or implicit', this sits at 3 rather than 4.

Progressive Disclosure

The body is under 50 lines with clean, well-labeled sections (Quick Reference, Check, Fix, Explain, Code Review) and a clearly signaled one-level-deep pointer — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — to a file that exists and holds exactly the deeper detail (code examples, directive table, verification procedures). This matches 'clear overview with well-signaled one-level-deep references; content appropriately split'.

Specificity

The description names one concrete action ("auditing robots meta tags") plus an applicability scope, matching the 'names domain and 1-2 concrete actions' anchor. It is not level 4 because it never states what specific defect is being audited (e.g., nosnippet or snippet suppression), and not level 2 because 'auditing robots meta tags' is a concrete, non-generic action.

Completeness

It has an explicit "Use when auditing robots meta tags" trigger and a clear applicability clause ("any important landing page, article, or product page that should appear with a description in search results"). Not level 5 because the 'what' side is thin — it does not state what problem is being detected or fixed (snippet suppression), only the general audit activity.

Trigger Term Quality

Terms like "robots meta tags", "search results", "landing page", "article", and "product page" are natural user phrasing, but the most common trigger terms for this exact skill — "nosnippet", "snippet", "max-snippet", and "meta description" — are entirely absent. This matches 'some relevant keywords but missing common variations or synonyms' rather than level 4's 'good keyword coverage with a few terms missing', since the core topic keywords are missing, not just a few.

Distinctiveness Conflict Risk

"Auditing robots meta tags" spans all robots directives (noindex, none, nofollow, max-image-preview), so it would trigger for sibling robots-directive SEO skills. It is somewhat specific but overlaps with closely related skills, matching the level 3 anchor rather than level 4's 'mostly distinct'.