Content
78%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 body is a lean, well-structured audit/fix guide with concrete, actionable specifics and an appropriately delegated one-level-deep reference file. Its main weaknesses are repetition of the doorway-page and areaServed guidance across sections and verification directions that stop short of explicit validation checkpoints.
Suggestions
State the doorway-page warning and areaServed schema guidance once (e.g., in Quick Reference) and have Check/Fix reference them rather than restate them, to trim repeated tokens.
Add an explicit validation checkpoint to the Fix workflow, e.g., "After publishing, verify the LocalBusiness/areaServed structured data with Google's Rich Results Test and spot-check each page for unique content".
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no explanations of concepts Claude already knows, but key facts repeat: the doorway-page warning appears in the intro ("thin, templated location pages are penalised by Google as doorway pages"), Quick Reference ("Avoid creating identical pages per location that differ only in the city name (doorway pages)"), and Check ("Flag pages that appear to be thin templated clones"), and the areaServed schema guidance appears in Quick Reference, Check, and Fix. Efficient with minor trimmable repetition — anchor 4. | 4 / 5 |
Actionability | Concrete, executable guidance throughout: "Use `LocalBusiness` schema with `areaServed`", "unique title targeting `[Service] in [City]`", "at least 300 words of unique content", "nearby landmarks, local case studies, region-specific FAQs". As an instruction-only skill the absence of inline code is acceptable, but the guidance stops short of copy-paste-ready examples (code lives in references/rule.md), so anchor 4 rather than 5. | 4 / 5 |
Workflow Clarity | A coherent Check → Fix → Explain → Code Review sequence covers audit, remediation, and code-level review, and the Code Review section directs verification ("describe how to verify the final page output"). However, explicit validation checkpoints (e.g., how to confirm schema validity or unique content per page) are not spelled out in the body — anchor 4, not 5. | 4 / 5 |
Progressive Disclosure | A clear under-50-line overview with a single well-signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — the file exists and contains the JSON-LD code example, per-page checklist, and verification steps. Content is appropriately split between overview body and detailed reference — anchor 5. | 5 / 5 |
Total | 17 / 20 Passed |