CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

content-security-policy

Use when reviewing headers, forms, cookies, or third-party integrations related to Implement a content security policy. Validate the effective browser and HTTP behavior in a production-like environment.

Quality

71%

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/content-security-policy/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 as an overview with excellent progressive disclosure to a real, one-level reference file carrying the executable details. Its weaknesses are mild redundancy — the sanitize/Trusted Types guidance repeated across five sections and a concept-explaining intro — and the absence of any concrete example or command in the body itself.

Suggestions

Cut the opening paragraph explaining what CSP prevents (Claude already knows this) and state the guidance once instead of repeating the sanitize/Trusted Types point across Quick Reference, Check, Fix, Explain, and Code Review.

Include one minimal concrete anchor in the body — e.g., a sample strict CSP header or a curl command to check the deployed header — so the Check step is executable before opening the reference.

Operationalize the verification checkpoint in the Code Review section with a specific action (e.g., 'curl -I the production-like URL and confirm the Content-Security-Policy header matches the intended policy').

DimensionReasoningScore

Conciseness

The opening paragraph explains what CSP defends against — a concept Claude already knows — and the sanitize/Trusted Types point is restated across five sections (Quick Reference, Check, Fix, Explain, Code Review). The body is otherwise short and tight, so this sits above the 'noticeably verbose' anchor but below 'efficient'.

3 / 5

Actionability

The Quick Reference gives specific, correct directives ('Start with Content-Security-Policy-Report-Only', 'Use nonces or hashes for inline scripts instead of unsafe-inline', 'Set strict default-src then allow specific sources'), but the body contains no example header, command, or code — all executable content is deferred to the reference file, leaving the guidance high-level.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review structure is a coherent sequence, and verification is explicitly instructed ('verify them against the effective production-like response', 'Validate the effective browser and HTTP behavior'). Not a 5 because checkpoints are named but not operationalized — no concrete verification commands are given.

4 / 5

Progressive Disclosure

A lean overview body with a single, clearly signaled, one-level-deep reference ('see references/rule.md', verified to exist) that appropriately holds the code examples, directive table, and framework-specific configuration. Navigation is easy and the split is right.

5 / 5

Total

15

/

20

Passed

Description

66%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 stated validation capability, placing it above the midpoint. However, the 'what' undersells the skill's actual scope, the CSP/XSS abbreviations users commonly say are absent, and the generic headers/forms/cookies triggers risk conflicts with sibling security rules.

Suggestions

State the core capability explicitly in the 'what' clause, e.g. 'Implements and reviews Content Security Policy (CSP) headers and directives' instead of only naming review targets.

Add the natural trigger phrases users actually say — 'CSP', 'Content-Security-Policy header', 'XSS protection' — and keep 'CSP' in the trigger clause to sharpen distinctiveness.

Tighten the trigger list so 'headers, forms, cookies, third-party integrations' are framed as CSP-related review targets, reducing overlap with sibling cookie/form security skills.

DimensionReasoningScore

Specificity

The description names the domain (content security policy) and 1-2 concrete actions — 'Validate the effective browser and HTTP behavior in a production-like environment' and 'reviewing headers, forms, cookies, or third-party integrations' — but does not comprehensively cover what the skill does (e.g., analyzing CSP directives, implementing headers, sanitization).

3 / 5

Completeness

Both parts are answered: an explicit 'Use when reviewing headers, forms, cookies...' clause gives the when, and 'Validate the effective browser and HTTP behavior in a production-like environment' gives the what. Not a 5 because the 'what' is thin — it never states the skill's core capability with CSP itself (implementing or reviewing the policy and its directives).

4 / 5

Trigger Term Quality

Natural keywords are present — 'headers', 'forms', 'cookies', 'third-party integrations', 'content security policy', 'browser', 'HTTP' — and a user would plausibly say these when needing this skill. A few common terms are missing, notably the 'CSP' abbreviation, 'XSS', and 'security headers'.

4 / 5

Distinctiveness Conflict Risk

The CSP niche is distinct, but the broad trigger list 'headers, forms, cookies, or third-party integrations' would also fire sibling security skills (cookie security, form hardening, header review), creating overlap risk with closely related skills.

3 / 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/content-security-policy/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.