Content
57%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured with good progressive disclosure to a real references/rule.md file and actionable audit/fix guidance with concrete inconsistency examples. It is dragged down by significant redundancy — duplicate Check/Code Review sections and a concept-explanation section Claude does not need — plus a missing post-fix verification step and the confusing "canonical-url format" wording.
Suggestions
Merge the 'Code Review' section into 'Check' — they are the same procedure written twice — and drop or compress 'Explain' and 'Quick Reference', since the NAP ranking-factor rationale is standard SEO knowledge already stated in the intro.
Fix the copy-paste error "a single canonical-url format" (appears in the Fix section) to read "a single canonical NAP format", so the instruction is not confused with URL canonicalization.
Add a validation step after the fix, e.g., "Re-scan the site and confirm every occurrence (including JSON-LD) now matches the canonical format exactly before finishing", to close the batch-update feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Several sections are padded or duplicated: "Code Review" restates "Check" almost verbatim ("Extract all instances of the business name, street address, and phone number... Compare each instance for exact formatting consistency" vs "Search the site for all instances of... Compare each occurrence for exact consistency"), the "Quick Reference" bullets restate the intro/Check/Fix, and "Explain" re-explains the same local-SEO ranking-factor concept already covered in the opening paragraph — knowledge Claude already has. This matches "noticeably verbose; several unnecessary explanations or padded sections" rather than anchor 3, because roughly a third of the body could be deleted with no information loss. | 2 / 5 |
Actionability | Concrete, specific guidance with real examples: "(e.g., 'St.' vs 'Street', '555-1234' vs '(555) 123-4567')" for comparison, and a fix that enumerates exact targets — "Update all pages, footer, contact page, about page, and structured data to match exactly". Not anchor 5 because there is no executable mechanism for finding all occurrences (e.g., a search command or extraction snippet), and the instruction "Standardise all NAP occurrences to a single canonical-url format" is confusing — a copy-paste error where "canonical NAP format" was meant. | 4 / 5 |
Workflow Clarity | A rough Check → Fix sequence is present ("Search the site for all instances..." then "Standardise all NAP occurrences...") but there is no verification step after the batch update of all pages and structured data, and the near-duplicate "Check"/"Code Review" sections blur which procedure to follow. Per the batch-operation cap (site-wide page updates with no validate/re-check loop), this cannot exceed 3, matching "sequence present but checkpoints missing or implicit". | 3 / 5 |
Progressive Disclosure | The short body is a clean overview with well-organized sections and one clearly signaled, one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and the file references/rule.md actually exists and itself contains no second-level references. This matches "clear overview with well-signaled one-level-deep references; easy navigation". | 5 / 5 |
Total | 14 / 20 Passed |