Content
71%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 well-structured, appropriately brief overview that correctly pushes detail to a real, clearly referenced bundle file. Its weakness is actionability — the Check section says what to verify but not how to detect generic anchors concretely — plus minor redundancy between the Check and Code Review sections.
Suggestions
Make the Check section concrete: give a detection method such as a grep/selector for generic anchors ('click here', 'read more', 'learn more', 'here') against the rendered HTML, or name the tooling to enumerate links.
Merge or differentiate the Check and Code Review sections, which currently repeat the same verification instruction, to remove redundancy.
Trim the intro sentence and Explain section that restate well-known anchor-text SEO/accessibility rationale, or move the rationale to references/rule.md where it already exists.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | A lean ~30-line body with clear one-line sections; the intro sentence and "Explain" section restate anchor-text SEO/accessibility concepts Claude already knows and could be trimmed, matching the minor-instances-of-over-explanation anchor. | 4 / 5 |
Actionability | Some concrete guidance ("Replace generic link text like 'click here' with descriptive phrases", "Flag exact routes or templates") but the Check section gives no detection method — no command, selector, or procedure for enumerating links in rendered HTML — leaving key execution details missing. | 3 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections form a clear sequence with verification guidance ("describe how to verify the final page output"). Not 5: Check and Code Review overlap redundantly and checkpoints are implicit rather than explicit. | 4 / 5 |
Progressive Disclosure | The body is a concise, well-organized overview that cleanly delegates implementation details, code examples, and verification to a single well-signaled one-level-deep reference ("see references/rule.md"), which exists and contains exactly that material. | 5 / 5 |
Total | 16 / 20 Passed |