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 title repeated with boilerplate metadata rather than a functional skill description. It lacks concrete actions, meaningful trigger terms, and any 'when to use' guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates HTTP security headers such as Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, and X-Content-Type-Options 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.'
Include diverse natural keywords users might say: 'CSP', 'CORS headers', 'X-Frame-Options', 'HSTS', 'web security headers', 'HTTP response headers', '.htaccess security'.
| 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 answer 'what does this do' beyond the name itself, and there is no explicit 'when to use' clause. The 'Triggers on' line is just a repeated label, 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 and narrows the domain compared to generic 'security' skills, but without concrete actions or file types, it could still 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 a placeholder or auto-generated stub with no substantive content. It contains no actual security headers information, no code examples, no specific header recommendations, and no actionable guidance whatsoever. Every section describes the skill in abstract terms rather than teaching Claude how to generate security headers.
Suggestions
Replace the meta-description sections with actual security header configurations (e.g., Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options) with concrete example values for common scenarios.
Add executable code examples showing how to set security headers in popular frameworks (Express.js, Django, nginx, Apache) so the skill is copy-paste actionable.
Include a validation step or checklist (e.g., 'Verify headers with `curl -I https://example.com` and check against securityheaders.com') to provide workflow clarity.
Remove all self-referential content ('This skill activates when...', 'Example Triggers') which wastes tokens without adding any instructional value.
| 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 vacuous. The entire body explains what the skill is rather than providing any actual security headers knowledge. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no specific headers, no example configurations, no commands. The skill describes itself abstractly without ever instructing Claude on how to actually generate security headers (e.g., Content-Security-Policy, X-Frame-Options, HSTS values, etc.). | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no useful structure. Sections like 'When to Use', 'Capabilities', and 'Example Triggers' describe the skill's metadata rather than organizing actionable content. No references to detailed resources or examples. | 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
3076d78
- 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.