Content
72%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 compact, well-structured overview with actionable check/fix guidance and exemplary progressive disclosure to a single verified reference file. Its main gaps are the absence of an explicit verification step after regenerating and resubmitting the sitemap, and minor duplication/meta-section content that could be trimmed.
Suggestions
Add an explicit validation checkpoint after the fix, e.g. 'After regenerating, re-run the domain/protocol check over the new sitemap and confirm zero mismatches before resubmitting, then verify coverage improves in Google Search Console.'
Remove the meta 'Explain' section (or fold it into the reference) — it instructs behavior Claude would exhibit unprompted — and drop the intro sentence duplicated verbatim from references/rule.md's 'Why It Matters'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and well-sectioned with no padding of concepts Claude already knows. Minor trimmable excess remains: the opening sentence is repeated verbatim in references/rule.md's 'Why It Matters', and the meta 'Explain' section ('Explain why Google restricts...') instructs behavior Claude would exhibit anyway. Fits anchor 4, not 5. | 4 / 5 |
Actionability | Concrete, executable guidance: 'Parse all <loc> values... extract the protocol and hostname. Flag any URL whose protocol or hostname differs from the sitemap's own URL', with enumerated mismatches (http/https, www/non-www, old/new domain) and a precise fix ('every sitemap URL must start with https://www.example.com/'). It falls short of 5 because no parsing command or snippet is shown inline — code examples live only in the reference. | 4 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sequence is clear and simply structured, but the fix ends with 'Regenerate and resubmit the sitemap' with no validation checkpoint (e.g., re-verify all <loc> values match after regeneration, or confirm coverage in Search Console). Per the feedback-loop rule for XML/sitemap batch manipulation, workflow_clarity is capped at 3. | 3 / 5 |
Progressive Disclosure | The ~45-line body is a concise overview with clearly labeled sections and a single, well-signaled, one-level-deep reference at the end ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), which exists and matches that description. This matches anchor 5. | 5 / 5 |
Total | 16 / 20 Passed |