Content
78%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 overview that keeps the body lean, names concrete artifacts to check, sequences the workflow audit-then-enforce-then-verify with explicit verification steps, and correctly pushes code examples and header values into a single, clearly signaled reference file. Remaining improvements are marginal: a trimmed intro paragraph and an explicit failure-handling step after verification.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and sectioned with no tutorial padding, but the intro paragraph ("reduces opener-based attacks and XS-Leak risk, and it is required for powerful browser features such as SharedArrayBuffer") reiterates background Claude already knows, and the Check/Fix sections partially restate each other. Minor trimming would reach the every-token-earns-its-place anchor at 5; there is not enough padding to drop to 3. | 4 / 5 |
Actionability | The guidance is largely executable: it names the exact headers (`Cross-Origin-Opener-Policy`, `Cross-Origin-Embedder-Policy`, `Cross-Origin-Resource-Policy`), the resource types to audit ("cross-origin script, iframe, image, worker, and font"), and a concrete runtime check (`self.crossOriginIsolated === true`). Minor gaps remain — no header values or commands inline (e.g. `require-corp`), which the body delegates to `references/rule.md`, keeping it below fully copy-paste-ready at 5 and well above pseudocode-level at 3. | 4 / 5 |
Workflow Clarity | A clear sequence is present — audit dependencies, then enforce headers, then verify — with an explicit validation checkpoint ("Verify `self.crossOriginIsolated === true` before depending on isolated-only features"; "verify the final document becomes crossOriginIsolated in the browser"). It stops short of a 5 because there is no explicit error-recovery loop for what to do when verification fails, though the Code Review section's instruction to "Flag exact responses or integrations that would block isolation" partially covers diagnosis. | 4 / 5 |
Progressive Disclosure | The ~45-line body is a clean overview whose implementation detail (header values, code examples, framework guidance) lives in `references/rule.md` — a real file, one level deep, containing exactly the code examples the body defers. The reference is clearly signaled ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"), matching the well-signaled one-level-deep anchor exactly. | 5 / 5 |
Total | 17 / 20 Passed |