Conciseness

The body is lean: terse Quick Reference bullets and one-line Check/Fix/Explain sections that assume Claude's competence, with details correctly deferred to references/rule.md. It is not 5 because the opening rationale sentence ('Structured author information helps search engines uniquely identify authors...') explains a 'why' Claude already knows and the Quick Reference partially duplicates the Fix section.

Actionability

The Fix and Quick Reference give concrete, specific instructions — 'Use JSON-LD', 'Include properties like name, url, sameAs, and jobTitle', 'Add a Person or Organization schema to your JSON-LD block and link it to the author property' — and point to a real reference file containing a full executable code example. It falls short of 5 because the Check and Code Review sections give no concrete method or tool for inspecting rendered HTML/headers (e.g., a view-source grep or Rich Results Test), leaving minor gaps.

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a coherent audit-fix-verify sequence with checkpoints (verify presence before fixing, then 'describe how to verify the final page output' after). It is not 5 because the verification checkpoint in the body is stated abstractly rather than as explicit steps or commands, though the referenced rule.md does carry a detailed Verification section.

Progressive Disclosure

The body is a well-organized ~45-line overview with clear sections and a single, clearly signaled one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), which exists and holds the code example, standards, and verification detail. This matches the anchor for a clear overview with well-signaled references and appropriate content split.

Specificity

The description names the domain ('auditing metadata, crawlability, structured data, or indexability') and offers roughly two concrete actions ('auditing' and 'Verify the rendered HTML and HTTP response'), matching the anchor for 1-2 concrete actions. It does not reach 4 because it lacks several specific actions, and it is above 2 because the actions are domain-specific rather than generic.

Completeness

Both parts are explicitly present: 'when' via 'Use when auditing metadata, crawlability, structured data, or indexability...' and 'what' via 'Implement comprehensive author markup' plus 'Verify the rendered HTML and HTTP response rather than relying only on source files.' It is not a 5 because the 'what' reads as a spliced task title rather than a crisply stated capability, and it is clearly above 3 since both what and when are explicit.

Trigger Term Quality

Terms like 'metadata', 'crawlability', 'structured data', 'indexability', 'rendered HTML', and 'HTTP response' are natural phrases an SEO auditor would say, giving good keyword coverage. It falls short of 5 because common synonyms such as 'schema markup', 'JSON-LD', 'rich results', and 'SEO' are missing, and exceeds 3 because multiple relevant natural terms are present rather than just a few.

Distinctiveness Conflict Risk

The trigger terms ('metadata', 'crawlability', 'structured data', 'indexability') are broad SEO-audit terms that would equally fire sibling SEO checklist skills, so overlap risk remains; only the embedded 'Implement comprehensive author markup' phrase distinguishes it. It is above 2 because it is anchored to a specific rule rather than documents in general, but below 4 because the generic SEO terms create real overlap with closely related skills.