Content
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is well-structured, concise, and uses progressive disclosure effectively with a verified one-level reference. Its main gaps are in the Check step's lack of a concrete fetching method/tool and the absence of an explicit post-fix verification loop.
Suggestions
Make the Check step executable by naming a concrete method or tool, e.g. "Fetch every <loc> with curl -o /dev/null -w '%{http_code}' or a crawler like Screaming Frog, then filter for 4XX."
Add an explicit verification loop after Fix, e.g. "Regenerate and resubmit the sitemap, then re-fetch to confirm no 4XX URLs remain and Search Console Coverage clears."
Surface one tiny code snippet or exact command inline in the body so the core check is copy-paste ready without opening the reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean (~40 lines), assumes Claude's competence without explaining what a sitemap or HTTP status code is, and every section (Quick Reference, Check, Fix, Explain, Code Review) earns its place; the Quick Reference is a legitimate summary pattern rather than padding. | 3 / 3 |
Actionability | Guidance names specific status codes and remediation ("set up a 301 redirect", "return 410 Gone", "Cross-reference against Google Search Console → Coverage"), but the Check step ("Fetch all URLs listed in the sitemap and record their HTTP status codes") gives no concrete method or tool, and the body carries no executable command or example (those live only in the reference). | 2 / 3 |
Workflow Clarity | A clear Check → Fix → Explain → Code Review sequence is present, but for a batch operation (fetching all sitemap URLs) and remediation changes there is no explicit post-fix validation or re-check loop; checkpoints are implicit, which caps it at 2 per the batch-operation guidance. | 2 / 3 |
Progressive Disclosure | The body is a well-organized overview with clearly signaled one-level-deep navigation ("see references/rule.md"), the referenced file exists and is a single level deep, and content is appropriately split between overview and details. | 3 / 3 |
Total | 10 / 12 Passed |