security-headers-configuration

Configures HTTP security headers to protect against XSS, clickjacking, and MIME sniffing attacks. Use when hardening web applications, passing security audits, or implementing Content Security Policy.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%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 content is concise and highly actionable with ready-to-use code for the common cases and good progressive disclosure to a real reference file. The main gap is workflow clarity: there is no explicit apply-then-verify-then-fix sequence, which matters for a configuration change that can break a site.

Suggestions

Add an explicit ordered workflow: configure headers -> deploy to a staging/preview -> verify with securityheaders.com or Mozilla Observatory -> fix any reported gaps before promoting.

Include a brief validation command or curl check (e.g. `curl -sI https://example.com | grep -i 'content-security-policy'`) so verification is concrete rather than only linked.

Note HSTS `preload` risk (irreversible domain listing) as a caution under the HSTS checklist item.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient: a compact header table plus two direct code blocks and a short checklist, with no padding or re-explanation of concepts Claude already knows.	5 / 5
Actionability	It provides copy-paste-ready Express/Node and Nginx code blocks plus a checklist of exact header values, covering the common implementation cases concretely.	5 / 5
Workflow Clarity	Although it is a simple skill, configuring security headers is a batch/deploy-style change that should be verified; the checklist exists but there is no validate-then-deploy sequence or feedback loop (e.g. 'test headers with securityheaders.com before promoting'), which caps workflow clarity at 3 per the destructive/batch guidance.	3 / 5
Progressive Disclosure	The SKILL.md is a concise overview with a clearly signaled, one-level-deep reference ([references/python-apache.md]) that exists as a real file, and supplementary material is appropriately split out.	5 / 5
	Total	18 / 20 Passed

Description

83%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 is strong: it states concrete capabilities, gives an explicit 'Use when' trigger, and occupies a clear niche. Minor improvements would add a couple of natural synonyms (e.g. 'security headers') to the trigger list.

Suggestions

Include the natural phrase 'security headers' explicitly as a trigger term, since users commonly say 'set up security headers'.

Add 1-2 more concrete actions beyond attack categories (e.g. 'sets HSTS, CSP, and X-Frame-Options headers') to raise specificity.

Dimension	Reasoning	Score
Specificity	It names the domain and several concrete actions ('Configures HTTP security headers to protect against XSS, clickjacking, and MIME sniffing attacks'), though it lists attack categories more than distinct concrete operations.	4 / 5
Completeness	It clearly states the 'what' (configures HTTP security headers against XSS/clickjacking/MIME sniffing) and an explicit 'when' clause ('Use when hardening web applications, passing security audits, or implementing Content Security Policy').	5 / 5
Trigger Term Quality	It includes natural user terms ('hardening web applications', 'passing security audits', 'Content Security Policy'), but is missing some common synonyms like 'security headers' as a standalone phrase.	4 / 5
Distinctiveness Conflict Risk	The security-headers niche has distinct, specific triggers unlikely to overlap with unrelated skills, and the named attacks make it clearly bounded.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: secondsky/claude-skills
Path: plugins/security-headers-configuration/skills/security-headers-configuration/SKILL.md
Commit: ad16332

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.