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 lean, well-structured overview with concrete check-and-fix guidance and an exemplary one-level-deep reference split — references/rule.md exists and delivers exactly what the pointer promises. The main weaknesses are mild redundancy (intro vs. Explain/Code Review sections) and the absence of any verbatim command or code snippet in the body itself.
Suggestions
Trim the intro's XSS-consequence explanation to one line and merge or cut the redundant "Explain" and "Code Review" sections, which restate the intro and the description.
Add one concrete executable artifact to the Check section, e.g. a ready-to-run grep/ripgrep pattern for eval(, new Function(, and string-argument timers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short, but the intro paragraph explains XSS consequences Claude already knows ("stealing sessions, making requests as the user, or redirecting to malicious sites"), and the "Explain" and "Code Review" sections largely restate the intro and the frontmatter description. It fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not 2 because there is no heavy padding and the Quick Reference is dense and useful. | 3 / 5 |
Actionability | "Search this codebase for any use of eval(), new Function(), or setTimeout/setInterval with string arguments" and "JSON.parse for data, object lookups for dynamic dispatch, and Function references for timers" give concrete, executable direction. It is not 5 because the body itself contains no verbatim command or code (e.g., an actual grep pattern or replacement snippet), deferring all examples to the reference file. | 4 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections form a clear, logical sequence and the operation is not destructive or batch, so no validation cap applies. It is not 5 because verification steps (which exist in references/rule.md) are not signaled in the body's workflow, and the "Code Review" section partially duplicates "Check", blurring the sequence. | 4 / 5 |
Progressive Disclosure | The body is a concise, well-sectioned overview (Quick Reference, Check, Fix, Explain, Code Review) and points to a single, clearly signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — a real, well-organized file covering code examples, safe alternatives, ESLint, CSP, and verification. Content is appropriately split with easy navigation. | 5 / 5 |
Total | 16 / 20 Passed |