Content
61%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 content is a well-structured, concise overview that appropriately delegates detail to a single real reference file. Its weaknesses are the lack of an executable validation command or code example inline and the absence of an explicit validate-then-fix feedback loop, which caps workflow clarity.
Suggestions
Add at least one executable validation command in the body, e.g. `xmllint --noout sitemap.xml` or a short fetch-and-check snippet, so the core action is copy-paste ready.
Insert an explicit validation checkpoint in the Check/Fix flow (validate against schema → if errors, fix encoding/limits → re-validate before resubmitting) to establish a feedback loop.
De-duplicate the namespace/encoding/limit facts between Quick Reference and Check so each section earns its tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and assumes Claude's knowledge of XML and sitemaps, but the Quick Reference and Check sections repeat the same namespace/encoding/limit facts, leaving minor redundancy that could be trimmed. | 4 / 5 |
Actionability | It gives concrete facts (namespace URI, encoding mappings, 50,000/50MB limits) but no executable command or code in the body itself — validation/fix steps are described abstractly ('Fetch the sitemap and validate it', 'Re-generate the sitemap using a validated sitemap library'), and the executable examples live only in the reference file. | 3 / 5 |
Workflow Clarity | The Check/Fix structure gives a rough sequence, but there is no explicit validation checkpoint or feedback loop for what is effectively a batch/destructive-adjacent XML operation, which per the rubric caps workflow clarity at 3. | 3 / 5 |
Progressive Disclosure | The body is a lean overview with a clearly signaled one-level-deep reference to references/rule.md (which exists), good sectioning (Quick Reference, Check, Fix, Explain, Code Review), and the bulk detail correctly delegated to the reference file. | 4 / 5 |
Total | 14 / 20 Passed |