Content
65%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.
A well-organized, token-efficient overview with excellent progressive disclosure to a single real reference file. The weaknesses are in the body's actionability (no inline executable code or commands) and workflow clarity (no post-fix validation checkpoint closing the loop).
Suggestions
Add one inline executable step to the Check section (e.g., 'curl -s https://example.com/sitemap.xml | head' or an XML validation command) so the body is not wholly dependent on the reference file for execution.
Close the workflow loop in Fix: instruct Claude to re-verify after generating or updating the sitemap (fetch it, confirm it parses as valid XML and includes the important pages).
Trim the duplicated 'why sitemaps matter' statement — keep it in either the intro or the Quick Reference bullet, not both.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean with clear sections, but the intro sentence 'Search engines may not discover all your pages through links alone—a sitemap ensures every important page gets indexed' and the Quick Reference bullet 'XML sitemaps help search engines discover all your pages' explain a concept Claude already knows and duplicate each other. Not 5 because these tokens do not earn their place; not 3 because only minor trimming is needed and there is no other padding. | 4 / 5 |
Actionability | Concrete specifics are named ('/sitemap.xml', 'Google Search Console and Bing Webmaster Tools', 'Reference sitemap in robots.txt'), but the Fix step ('Generate or update the XML sitemap... with proper priority and changefreq values') is high-level direction — every executable code example and command is deferred to references/rule.md rather than included or sampled inline. Not 4 because the body itself contains no executable code or commands; not 2 because specific tools and paths are named. | 3 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections form a coherent rough sequence, and Check ('Verify that this website has a valid XML sitemap accessible at /sitemap.xml') acts as an implicit pre-checkpoint, but there is no post-fix re-validation and 'describe how to verify the final page output' defers verification rather than specifying it. Matches anchor 3: sequence present but checkpoints missing or implicit. | 3 / 5 |
Progressive Disclosure | A lean ~30-line overview with a clearly signaled, one-level-deep pointer: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md'. The referenced file exists, holds the executable details appropriately split from the overview, and nests no further references. Matches the anchor-5 example of a clear overview with well-signaled single-level references. | 5 / 5 |
Total | 15 / 20 Passed |