CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cross-origin-security

Use when reviewing scripts, client components, bundles, or runtime behavior related to Handle cross-origin requests securely. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/cross-origin-security/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

The body is well structured with an excellent progressive-disclosure split — a lean overview correctly pushing code and framework guidance to the existing one-level-deep rule.md. Its weaknesses are redundancy (the SOP explainer and Check/Fix/Explain/Code Review prose restate the Quick Reference bullets) and the absence of any concrete code or commands in the body itself, leaving the Check/Fix guidance at the prose level.

Suggestions

Drop or compress the Same-Origin Policy intro paragraph — Claude already knows SOP/CORS basics — and let the reference's 'Why It Matters' section carry that context.

Collapse the overlapping Check/Fix/Explain/Code Review prose into the Quick Reference bullets plus one review-workflow step list, eliminating the near-verbatim repetition of the description.

Inline one tiny good/bad snippet (e.g. the ALLOWED_ORIGINS postMessage guard) so the most common fix is executable directly from the body without opening the reference.

DimensionReasoningScore

Conciseness

The body opens by explaining the Same-Origin Policy — 'The Same-Origin Policy is the browser's primary defense against malicious sites stealing data' — which is knowledge Claude already has, and the Check/Fix/Explain/Code Review prose sections substantially restate the Quick Reference bullets and each other (e.g. 'Review scripts, client components, and browser execution paths' repeats the description nearly verbatim). Mostly efficient, but it could be tightened to the bullet list plus the reference pointer.

3 / 5

Actionability

The Quick Reference bullets name exact, checkable patterns ('verify event.origin before processing postMessage data', 'Never set Access-Control-Allow-Origin: * for authenticated endpoints', 'Reject unvalidated redirect targets such as `next`, `redirect`, or `callbackUrl`'), but the body itself contains no code or commands — all executable examples are deferred to references/rule.md, and the Check/Fix sections are prose descriptions ('Add origin validation to postMessage listeners and review CORS configuration') rather than concrete steps.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a clear, coherent review sequence, and the Code Review section explicitly requires stating 'how the change should be verified in the browser', with detailed verification steps one level deep in rule.md. Not a 5 because the validation loop (verify → fix → re-verify) is referenced rather than laid out as explicit checkpoints in the body.

4 / 5

Progressive Disclosure

A ~35-line, well-sectioned overview that defers all implementation detail via a clearly signaled, one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`' — and that file exists and appropriately carries the code examples and verification steps. Structure and split match the top anchor.

5 / 5

Total

15

/

20

Passed

Description

62%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.

The description has an explicit 'Use when' trigger and a recognizable security niche, but it embeds the rule title mid-sentence ('related to Handle cross-origin requests securely'), which garbles the capability statement, and it omits the natural domain keywords (CORS, postMessage, CSRF) users would most likely say. It sits at or slightly above the midpoint: functional, but not crisp.

Suggestions

Rewrite the capability statement so the rule title is not embedded mid-sentence — e.g. 'Reviews scripts, client components, and browser runtime behavior for cross-origin security issues (CORS misconfiguration, unvalidated postMessage origins, CSRF, open redirects). Use when auditing code for CORS, postMessage, or cross-origin request security.'

Add the natural trigger terms users would say — 'CORS', 'postMessage', 'CSRF', 'open redirect', 'SameSite' — to the trigger clause so the skill matches how the need is actually voiced.

Move the browser-verification intent ('fixes target the real bottleneck or bug') into a concrete verb list so the 'what' enumerates several specific actions instead of two.

DimensionReasoningScore

Specificity

Names the cross-origin security domain and two concrete actions ('reviewing scripts, client components, bundles, or runtime behavior', 'Inspect both source code and the browser execution path'), but coverage is not comprehensive — CORS configuration, postMessage validation, CSRF, and redirect handling are never named as actions.

3 / 5

Completeness

Both parts are present: an explicit 'Use when reviewing scripts, client components, bundles, or runtime behavior…' trigger and a 'what' ('Inspect both source code and the browser execution path so fixes target the real bottleneck or bug'). Not a 5 because the what-clause is weakened by the awkward embedded phrase 'related to Handle cross-origin requests securely', which reads as template concatenation rather than a clear capability statement.

4 / 5

Trigger Term Quality

'cross-origin requests' is the natural key term, but the common variations users would actually say — 'CORS', 'postMessage', 'CSRF', 'open redirect' — are missing, and the remaining keywords ('scripts', 'client components', 'bundles') are generic frontend vocabulary rather than domain triggers.

3 / 5

Distinctiveness Conflict Risk

The cross-origin security niche has fairly distinct triggers and would rarely fire for unrelated skills, but the broad opener 'reviewing scripts, client components, bundles, or runtime behavior' overlaps with general frontend code-review skills, creating minor conflict risk.

4 / 5

Total

14

/

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-security/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.