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.
A clean, well-structured overview that delegates implementation detail to a real, clearly-signaled reference file. The body itself is weakened by redundancy (Check vs Code Review), a motivational intro Claude does not need, and the absence of any concrete technique for its central task — deciding when a collected field is truly unconsumed.
Suggestions
Merge the near-duplicate "Check" and "Code Review" sections into one, and drop or compress the "why it matters" intro — the Explain section already covers the rationale for the user.
Add one concrete inline heuristic or command for the core verification step, e.g. "grep the codebase for reads of the field/key before flagging it as unconsumed", so the audit is executable without opening the reference.
Reorder sections into a single check-then-fix flow with an explicit validation point (confirm unused, then remove/anonymise, then re-check the payload) to give the workflow checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly tight, but the motivational intro paragraph ("increases the blast radius of a breach, exposes your organisation to regulatory fines, and erodes user trust") explains context Claude already knows, and the "Check" and "Code Review" sections are near-duplicates of each other (both audit form fields/fetch calls/storage keys plus analytics payloads for raw PII). Mostly efficient but could be meaningfully tightened, matching anchor 3. | 3 / 5 |
Actionability | Concrete audit targets are named ("form components, fetch/axios calls, and storage utilities"; "raw email addresses, names, phone numbers, or full query strings"), but the body contains no executable method for its core step — no commands or heuristics for verifying a field is truly unused, and all code examples are deferred to references/rule.md. Some concrete guidance but incomplete, matching anchor 3. | 3 / 5 |
Workflow Clarity | The sections (Quick Reference, Check, Fix, Explain, Code Review) form a recognizable check-then-fix sequence, but there are no validation checkpoints (e.g. confirming a field is unread by grepping for consumers before flagging it), and "Code Review" sits oddly after "Fix" as a restatement of "Check". Steps listed with validation gaps, matching anchor 3. | 3 / 5 |
Progressive Disclosure | The body is a lean under-50-line overview with a clearly signaled, one-level-deep pointer ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md") to a real file that carries the code examples and detailed guidance. Overview and detail are appropriately split with easy navigation, matching anchor 5. | 5 / 5 |
Total | 14 / 20 Passed |