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.
The body is a lean, well-organized overview with exemplary progressive disclosure into a real one-level reference file. Its weakness is execution detail: the Check and Fix steps are high-level directions with no concrete scan/verify procedure, and the workflow lacks an explicit post-fix validation loop in the body itself.
Suggestions
Add a concrete, executable check step, e.g. extracting internal hrefs from rendered HTML and checking each with curl's status code output, instead of the bare 'Scan the website' instruction.
Insert an explicit validation loop after Fix — re-crawl the affected routes and confirm the links no longer return 404/5xx before considering the rule satisfied — rather than deferring all verification to the reference file.
Inline the one or two most important verification commands from references/rule.md (e.g. inspecting rendered HTML and HTTP headers) so the main workflow is self-sufficient.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~30-line body is tightly sectioned (Quick Reference, Check, Fix, Explain, Code Review) with almost no padding; the single motivational opener ('frustrate users and waste crawl budget...') explains a concept Claude already knows, a minor trimmable instance matching anchor 4. Not 3 because there are no padded sections beyond that one sentence. | 4 / 5 |
Actionability | Some concrete guidance exists — specific status codes ('404 (Not Found) or 5xx (Server Error)'), 'Flag exact routes or templates', 'verify the final page output' — but the core operations are high-level hints: 'Scan the website for any internal links' and 'Update the broken link to the correct URL' give no command, tool, or procedure. This fits 'some concrete guidance but incomplete; missing key details' rather than anchor 4's mostly-executable guidance. | 3 / 5 |
Workflow Clarity | A sequence is present (Quick Reference → Check → Fix → Explain → Code Review) but validation checkpoints are only implicit ('describe how to verify the final page output'), with the actual verification steps (re-crawl, Search Console check) living solely in the reference file. Because link scanning is a batch operation with no explicit validate-after-fix feedback loop in the body, workflow clarity is capped at 3 per the rubric's feedback-loops guidance. | 3 / 5 |
Progressive Disclosure | The body is a short, well-sectioned overview with one clearly signaled, one-level-deep reference ('see references/rule.md') that exists and appropriately holds the implementation details, code example, and verification procedures. This matches the top anchor: clear overview, appropriately split content, easy navigation. | 5 / 5 |
Total | 15 / 20 Passed |