CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cross-origin-isolation

Use when reviewing security-sensitive web apps, SharedArrayBuffer usage, worker-heavy apps, editors, or measurement features that require cross-origin isolation. Check both headers and real browser behavior.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews 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.

DimensionReasoningScore

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

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit, concrete 'Use when' trigger clause and a clear statement of what the skill checks. Its main weakness is that the 'what' sentence stays high-level rather than enumerating the specific checks the skill performs.

Suggestions

Expand the 'what' sentence to enumerate the concrete actions, e.g. "Audit cross-origin embeds, review COOP/COEP/CORP headers, and verify `self.crossOriginIsolated === true` in the browser."

Add the header acronyms COOP, COEP, and CORP (and `crossOriginIsolated`) as trigger terms, since users needing this skill often phrase the request in those terms.

DimensionReasoningScore

Specificity

The description names the domain ("cross-origin isolation") and offers 1-2 concrete actions ("Check both headers and real browser behavior"), but does not enumerate several specific actions such as auditing cross-origin embeds or verifying `self.crossOriginIsolated`. It sits at the 'domain and 1-2 concrete actions' anchor rather than the 'several specific actions' anchor above, and well above the 'names domain, generic actions' anchor below.

3 / 5

Completeness

It explicitly answers both questions: the 'what' is "Check both headers and real browser behavior", and the 'when' is a concrete "Use when reviewing..." clause listing multiple trigger contexts (SharedArrayBuffer usage, worker-heavy apps, editors, measurement features). The 'when' is specific and trigger-phrase-rich, so it does not fit the anchor at 4 where the 'when' is only weakly specified.

5 / 5

Trigger Term Quality

Natural phrases like "SharedArrayBuffer usage", "worker-heavy apps", "security-sensitive web apps", and "cross-origin isolation" match what developers would actually say. A few natural terms are missing — most notably the header acronyms COOP, COEP, and CORP and `crossOriginIsolated` — which keeps it below the comprehensive-coverage anchor at 5 but above the sparse-keywords anchor at 3.

4 / 5

Distinctiveness Conflict Risk

Distinctive technical markers ("SharedArrayBuffer", "cross-origin isolation") carve out a clear niche, though the broad opening phrase "security-sensitive web apps" creates minor overlap risk with general security-review skills. This places it between the 'clear niche, minimal conflict' (5) and 'somewhat specific, some overlap' (3) anchors, noticeably above the midpoint.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/cross-origin-isolation/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.