Content
57%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 well-structured with excellent progressive disclosure — a concise overview pointing to a real, one-level-deep reference holding the details. Its weaknesses are duplicated conceptual content between body and reference, and body-level guidance that stays high-level because the concrete commands and verification steps all live in the reference file.
Suggestions
Remove the intro/Why-It-Matters paragraph duplicated verbatim in references/rule.md and fold the Quick Reference bullets into Check/Fix to eliminate repetition.
Surface one or two executable checks directly in the body (e.g. the curl Set-Cookie audit command or the DevTools 'Third-party requests' filter) so the Check section is actionable without opening the reference.
Make the verification checkpoint explicit in the Code Review section (e.g. 'Confirm in the production-like response that no non-essential Set-Cookie headers fire before consent') rather than a single vague 'verify' mention.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph ('Third-party cookies enable advertising networks to build detailed behavioral profiles... 4% of global annual turnover') explains background Claude already knows and is repeated verbatim in references/rule.md ('Why It Matters'), and the Quick Reference bullets duplicate content from the Check/Fix sections and the reference. Mostly efficient but should be tightened — anchor 3, not 4, because of the duplicated conceptual padding. | 3 / 5 |
Actionability | 'Open the browser DevTools Network panel and Application panel (Cookies section)' is concrete, but the Fix section is high-level direction ('Audit and remove unnecessary third-party scripts. Replace cross-site tracking with privacy-preserving first-party analytics') with no commands in the body — the executable specifics (curl audit, DevTools third-party filter, SameSite examples) are all deferred to the reference. Fits anchor 3 ('Some concrete guidance but incomplete; missing key details'). | 3 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sequence is coherent and this is not a destructive/batch operation, but validation is only one vague mention ('verify them against the effective production-like response') with the real verification steps (production-like testing, manual response inspection) deferred to the reference. Anchor 3 ('sequence present but checkpoints missing or implicit') fits better than 4. | 3 / 5 |
Progressive Disclosure | The body is a ~35-line, cleanly sectioned overview with a single clearly-signaled one-level-deep reference (references/rule.md, verified to exist, no nested references), and the bulk detail — tables, code examples, verification steps — is appropriately split into that reference. This matches anchor 5 ('Clear overview with well-signaled one-level-deep references; content appropriately split'). | 5 / 5 |
Total | 14 / 20 Passed |