Content
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is concise and well-structured with proper progressive disclosure to a real reference file. It falls short on actionability and workflow clarity because the body offers prose directives rather than executable commands and lacks explicit validation checkpoints for a change that can delist a site.
Suggestions
Add an executable check command to the Check section, e.g. `curl -I "$ORIGIN/robots.txt"` and a grep for `Disallow: /`, so guidance is copy-paste ready.
Insert an explicit validate-then-proceed checkpoint (fetch, verify HTTP 200 and no site-wide Disallow, only then edit) to support the risky crawl-affecting change.
Move or mirror the concrete robots.txt directive example from the reference into the Fix section so the body stands on its own.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — short Quick Reference, Check, Fix, Explain, and Code Review sections with no padding or explanation of basic concepts. | 3 / 3 |
Actionability | The Check/Fix sections give concrete direction ('Fetch /robots.txt... verify HTTP 200', 'Add a live Sitemap: line', 'Remove any Disallow: / rules') but no executable commands or code in the body itself, so guidance is actionable but not copy-paste ready. | 2 / 3 |
Workflow Clarity | The Check→Fix→Explain→Code Review sections imply a sequence, but there are no explicit validation checkpoints or verify-then-fix feedback loops in the body for this crawl-affecting change. | 2 / 3 |
Progressive Disclosure | A concise overview body signals a single one-level-deep reference ('see references/rule.md') that exists, with content appropriately split between the overview and the detailed rule page. | 3 / 3 |
Total | 10 / 12 Passed |