Content
71%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 well-structured overview with strong progressive disclosure: it defers code examples and framework guidance to a real, substantive references/rule.md and keeps only the essentials inline. Its weaknesses are redundancy — the required-field list appears four times, with Check and Code Review nearly duplicating each other — and explanation of LocalBusiness-schema basics that Claude already knows.
Suggestions
Merge the 'Check' and 'Code Review' sections, which repeat nearly identical detection criteria and required-field lists.
Drop or compress the 'Explain' section and the intro paragraph, which duplicate each other in stating what LocalBusiness schema does (knowledge Claude already has).
State the required-field list once (e.g., in Quick Reference) and reference it from the other sections instead of restating it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is compact overall, but the required-properties list is repeated across Quick Reference, Check, Fix, and Code Review (e.g., 'Verify the required properties are present: name, address with PostalAddress, telephone, and url' vs. the near-identical Code Review list), and both the intro paragraph and the Explain section restate what LocalBusiness schema does — knowledge Claude already has. It is not a 2 because each section is terse with no heavy padding, and not a 4 because the Check/Code Review duplication and the Explain section are genuinely trimmable. | 3 / 5 |
Actionability | The Fix section gives a complete, executable spec — 'Add a <script type='application/ld+json'> block ... Include: @context, @type, name, address (with streetAddress, addressLocality, addressRegion, postalCode, addressCountry), telephone, url, openingHours, and geo' — and both Check and Code Review name a concrete validation tool (Google's Rich Results Test). It is not a 5 because the body itself contains no copy-paste-ready JSON-LD example (code is deferred to references/rule.md), and not a 3 because the guidance is specific and complete rather than high-level hints or pseudocode. | 4 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review section order implies a clear check/add/validate sequence, and the validation checkpoint ('Validate with Google's Rich Results Test') is present in both Check and Code Review. It is not a 5 because the sequence is implied by section order rather than stated and there is no explicit re-validate-after-fixing feedback loop, and not a 3 because a validation tool is named and the single action (add LocalBusiness JSON-LD) is unambiguous. | 4 / 5 |
Progressive Disclosure | The body is a lean overview with clear sections and a single, well-signaled, one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and that file exists and carries the bulk detail (full JSON-LD examples, property tables, sub-type list, Next.js implementation, validation, exceptions). This matches the anchor for a clear overview with appropriately split content and easy navigation. | 5 / 5 |
Total | 16 / 20 Passed |