security-policy-generator
Security Policy Generator - Auto-activating skill for Security Advanced. Triggers on: security policy generator, security policy generator Part of the Security Advanced skill category.
33
0%
Does it follow best practices?
Impact
97%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/04-security-advanced/security-policy-generator/SKILL.mdQuality
Discovery
0%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's name without providing any substantive information about its capabilities, use cases, or trigger conditions. It lacks concrete actions, natural trigger terms, explicit 'when to use' guidance, and any distinguishing detail that would help Claude select it appropriately from a pool of skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates security policies including access control policies, data protection policies, incident response plans, and acceptable use policies.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create, draft, or review security policies, compliance documents, or information security guidelines.'
Remove the redundant duplicate trigger term and instead include varied natural keywords users might say, such as 'security policy', 'compliance policy', 'infosec policy', 'data protection policy', 'access control policy'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names no concrete actions whatsoever. It says 'Security Policy Generator' but does not describe what it actually does—no mention of generating, reviewing, formatting, or any specific capabilities. | 1 / 3 |
Completeness | Neither the 'what' nor the 'when' is meaningfully answered. There is no explanation of what the skill does beyond its name, and no explicit 'Use when...' clause or equivalent guidance for when Claude should select it. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'security policy generator' repeated twice. It misses natural user phrases like 'create security policy', 'compliance policy', 'access control policy', 'information security', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Security Advanced' and 'security policy generator' provide no clear niche. It could easily conflict with any other security-related skill and offers no distinguishing detail. | 1 / 3 |
Total | 4 / 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 an empty shell with no substantive content. It repeatedly names 'security policy generator' without ever defining what a security policy looks like, how to generate one, what frameworks to follow (e.g., NIST, ISO 27001, SOC2, GDPR), or providing any templates, examples, or executable guidance. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable templates for common security policies (e.g., an access control policy template, incident response policy template) with specific sections and example content.
Include a clear multi-step workflow: 1) Identify policy scope/framework, 2) Select template, 3) Customize sections, 4) Validate against compliance requirements, 5) Output final document — with validation checkpoints.
Remove all generic boilerplate ('This skill provides automated assistance...') and replace with actionable content such as framework-specific checklists (SOC2 controls, GDPR articles) and mapping tables.
Add references to detailed sub-files for specific frameworks (e.g., 'See SOC2_POLICY.md for SOC2-specific templates' and 'See GDPR_POLICY.md for GDPR data protection policies').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'security policy generator' excessively, and provides zero substantive information about how to actually generate security policies. | 1 / 3 |
Actionability | There are no concrete steps, code examples, commands, templates, or specific guidance. Every section is vague and abstract — 'Provides step-by-step guidance' without actually providing any steps. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints — just generic claims about capabilities without any actual process. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic text with no references to detailed materials, no links to templates or examples, and no meaningful structure beyond boilerplate headings. | 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.