CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

76

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, concise, and actionable skill body with excellent progressive disclosure and executable examples. The only gap is workflow_clarity: the verification tools are not framed as an explicit validate-and-fix sequence.

Suggestions

Add an explicit ordered workflow such as: 1) apply headers, 2) verify with securityheaders.com/Mozilla Observatory, 3) fix any flagged gaps and re-verify, so the validation feedback loop is explicit rather than implied by the checklist and tool list.

Consider noting one concrete pass-threshold from the verification tools (e.g., target an A grade) to make the validation checkpoint actionable rather than open-ended.

DimensionReasoningScore

Conciseness

The body is lean with no padding explaining what XSS/HSTS/CSP are; each section (header table, two code blocks, tools, checklist) earns its place and assumes Claude's competence.

3 / 3

Actionability

Provides two complete, copy-paste-ready executable code blocks (Express helmet directive config and Nginx add_header lines) plus concrete header values in the table, matching the fully-executable anchor.

3 / 3

Workflow Clarity

A checklist and verification tools are present, but there is no explicit configure -> verify -> fix feedback loop wired as a sequenced workflow, leaving validation checkpoints implicit rather than explicit.

2 / 3

Progressive Disclosure

The body is a concise overview with a clearly signaled, one-level-deep reference to references/python-apache.md (a real file), with content appropriately split between main skill (Express/Nginx) and reference (Flask/Apache).

3 / 3

Total

11

/

12

Passed

Description

100%

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: third-person, concise, and explicit about both capability and trigger conditions with concrete attack-type specifics. No changes needed.

DimensionReasoningScore

Specificity

Names a concrete domain (HTTP security headers) and enumerates specific protective actions against three named attack types ("XSS, clickjacking, and MIME sniffing attacks"), matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly states what it does ("Configures HTTP security headers to protect against...") and gives an explicit "Use when..." trigger clause, answering both what and when.

3 / 3

Trigger Term Quality

"hardening web applications", "passing security audits", and "implementing Content Security Policy" are natural phrases a user would say when requesting this skill, with good coverage of the domain's vocabulary.

3 / 3

Distinctiveness Conflict Risk

The security-headers niche with specific triggers like "Content Security Policy" and named browser attacks makes it clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
secondsky/claude-skills
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.