Content
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is well-structured with a clean overview and a properly signaled single reference, scoring well on progressive disclosure. Its weaknesses are token redundancy between Quick Reference and Check, the absence of any executable command in the body, and a missing re-validation checkpoint in the Fix workflow.
Suggestions
De-duplicate Quick Reference and Check: keep Quick Reference as the spec list and make Check a concrete validation procedure (e.g. `xmllint --noout sitemap.xml`) instead of restating the limits.
Add at least one executable command to the body (such as the xmllint invocation or a validator URL) rather than deferring all tooling to the reference.
Insert an explicit re-validation step in Fix before "Resubmit to Google Search Console" to form a validate→fix→re-validate→resubmit feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean with bullet points and no tutorial padding, but the "Check" section restates the Quick Reference limits and namespace in prose (e.g. 50,000 URLs / 50 MB and the xmlns value appear twice). It is above 1 because there is no concept over-explanation, but below 3 due to this redundancy. | 2 / 3 |
Actionability | Concrete specifics are present (exact namespace URL, 50,000-URL/50-MB limits, encoding table), but the body gives no executable command or code — "validate it against the sitemaps.org schema" and "re-generate using a validated sitemap library" are procedural without the how, deferred to the reference. It is not 1 because real specifics exist, and not 3 because nothing in the body is copy-paste executable. | 2 / 3 |
Workflow Clarity | A Check→Fix sequence is present (check the sitemap, then re-generate/encode/split/resubmit), but there is no explicit re-validation checkpoint before resubmitting. Per the scoring notes, missing validation feedback in batch/XML operations caps this at 2; it is above 1 because steps are listed and ordered. | 2 / 3 |
Progressive Disclosure | The body is a concise, well-sectioned overview (Quick Reference, Check, Fix, Explain, Code Review) that points to one clearly-signaled, one-level-deep real file ("see references/rule.md"), and rule.md is self-contained with no nested references. It matches the clear-overview-with-one-level-reference anchor rather than the score 2 inline-bloat or score 1 nested-reference patterns. | 3 / 3 |
Total | 9 / 12 Passed |