security-headers-generator
Security Headers Generator - Auto-activating skill for Security Fundamentals. Triggers on: security headers generator, security headers generator Part of the Security Fundamentals skill category.
35
3%
Does it follow best practices?
Impact
93%
0.97xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/03-security-fundamentals/security-headers-generator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that restates the skill name without providing any meaningful detail about capabilities, use cases, or trigger scenarios. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from other security-related skills in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates HTTP security headers including Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy for web applications.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about HTTP security headers, CSP policies, HSTS configuration, XSS protection headers, or hardening web server responses.'
Remove the duplicated trigger term and expand with varied natural language terms users would actually say, such as 'secure my website headers', 'add CSP', 'configure HSTS', 'prevent clickjacking'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('security headers') but does not describe any concrete actions. There is no mention of what the skill actually does—no verbs like 'generates', 'configures', 'analyzes', or lists of specific capabilities. | 1 / 3 |
Completeness | The description fails to clearly answer 'what does this do' beyond the name itself, and there is no explicit 'when to use' clause. The 'Triggers on' line is just the skill name repeated, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'security headers generator' repeated twice. It lacks natural variations users might say such as 'HTTP headers', 'CSP', 'Content-Security-Policy', 'HSTS', 'X-Frame-Options', 'web security', or 'add security headers'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'security headers' is somewhat specific to a niche (HTTP security headers), which provides some distinctiveness. However, the lack of concrete actions and the vague 'Security Fundamentals' category could cause overlap with other security-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially an empty shell with no actionable content. It contains only generic meta-descriptions of what it claims to do without any actual security header configurations, code examples, or concrete guidance. It fails on every dimension because it provides zero useful information that Claude could act on.
Suggestions
Add concrete, executable code examples showing how to set security headers (e.g., Content-Security-Policy, X-Frame-Options, Strict-Transport-Security) for common frameworks like Express.js, Django, or nginx configs.
Include a checklist or table of recommended security headers with their values and explanations of what each prevents (e.g., XSS, clickjacking).
Add a validation step, such as using `curl -I` to verify headers are set correctly, or referencing tools like securityheaders.com for automated checking.
Remove all the meta-description sections ('Purpose', 'When to Use', 'Example Triggers') and replace with actual instructional content that teaches how to generate and configure security headers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler text that tells Claude nothing useful. Phrases like 'This skill provides automated assistance for security headers generator tasks' and 'Follows industry best practices and patterns' are vague boilerplate. No actual security header content or configuration is provided. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no specific security headers listed, no configuration snippets, no commands. The entire content describes rather than instructs, offering only abstract platitudes about what the skill does. | 1 / 3 |
Workflow Clarity | There is no workflow, no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. A security headers generator should at minimum show how to configure headers and verify them. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic text with no meaningful structure. Section headers exist but contain no substantive content. There are no references to detailed materials, examples files, or related documentation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
87f14eb
- 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.