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.
A well-structured, appropriately brief overview body with concrete audit guidance and proper progressive disclosure to an existing reference file. The main issues are duplicated Quick Reference content and the absence of any executable snippet or example header.
Suggestions
De-duplicate the Quick Reference: merge the two 'upgrade-insecure-requests' bullets into one, and remove the repetition of the active/passive distinction (it reappears in the Explain section).
Add one concrete example, such as the literal header line 'Content-Security-Policy: upgrade-insecure-requests' as an HTTP response header, or a grep command for scanning source files for http:// URLs.
In the Code Review section, state what to do when verification fails (fix and re-verify) to close the workflow feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean, but 'upgrade-insecure-requests' appears three times (two Quick Reference bullets plus the Fix section) and the active/passive mixed-content distinction is repeated in both Quick Reference and Explain. This redundancy goes beyond the minor trimming of anchor 4. | 3 / 5 |
Actionability | Concrete instruction-only guidance: exact attributes to inspect ('<script src>, <img src>, <link href>, <iframe src>, and CSS url() values for http:// URLs') and a specific fix directive ('Content-Security-Policy: upgrade-insecure-requests'). Minor gaps — no example CSP header line or concrete scan command — keep it below 5. | 4 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review section order forms a clear sequence, and the Code Review section adds a verification checkpoint ('verify them against the effective production-like response'). No explicit feedback loop for failed verification, so not 5. | 4 / 5 |
Progressive Disclosure | The ~45-line body is a well-sectioned overview (Quick Reference, Check, Fix, Explain, Code Review) that delegates implementation details, code examples, and framework guidance to a clearly signaled one-level-deep pointer ('see references/rule.md'), which exists in the bundle. | 5 / 5 |
Total | 16 / 20 Passed |