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, concise overview with excellent progressive disclosure — the heavy detail (code examples, framework guidance) correctly lives in references/rule.md. Its main weakness is actionability: the Check and Fix steps say what to do but not how, with no inline command or example to make the audit immediately executable.
Suggestions
Add one executable check to the Check section, e.g. `curl -s https://example.com/page | grep -i 'rel="canonical"'` or a note to inspect the DOM in devtools, so the audit step is immediately actionable rather than deferred to the reference.
Inline a minimal correct example in the Fix section (e.g. `<link rel="canonical" href="https://example.com/page" />`) so the fix target is concrete without leaving the body.
Cut the redundant concept bullets in Quick Reference (the first two duplicate the intro paragraph) and fold the useful specifics (absolute URLs, self-referencing canonicals) into Check/Fix where they guide action.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 45-line body is lean and directive, but the intro paragraph and the first two Quick Reference bullets ("Canonical URLs tell search engines which version of a page to index", "Prevents duplicate content penalties from URL variations") restate basics Claude already knows and duplicate each other — minor over-explanation that could be trimmed. | 4 / 5 |
Actionability | The Check section gives a specific instruction ("Verify that this page has a canonical URL tag and that it points to the correct preferred version") but no executable method — no command for inspecting rendered HTML versus source, no example canonical tag, and no framework-level pointer inline; the concrete how is entirely deferred to references/rule.md. Anchor 3: some concrete guidance but missing key details. | 3 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections form a clear, coherent sequence for a single-rule audit. Not 5 because there are minor validation gaps: no explicit post-fix verification step and no instruction for how to confirm the canonical in rendered output (the description's key behavior) inside the body's Check step. | 4 / 5 |
Progressive Disclosure | The body is a clean overview with clearly labeled sections, and full implementation details, code examples, and framework-specific guidance are appropriately split into references/rule.md — a well-signaled, one-level-deep reference that exists in the bundle (verified), with no nested reference chains. | 5 / 5 |
Total | 16 / 20 Passed |