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.
36
Quality
3%
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
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 severely underdeveloped - it's essentially just a title with metadata rather than a functional description. It provides no information about what the skill actually does, what types of security policies it generates, or in what situations Claude should select it. The redundant trigger term and category reference add no value for skill selection.
Suggestions
Add specific capabilities describing what the skill does, e.g., 'Generates security policies including access control policies, data protection guidelines, incident response procedures, and compliance documentation.'
Include a proper 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user asks about creating security policies, compliance requirements, access controls, or organizational security documentation.'
Add natural keyword variations users might say: 'security guidelines', 'compliance policy', 'access policy', 'data protection policy', 'security standards', 'infosec policies'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only names itself ('Security Policy Generator') without explaining what it actually does. There are no verbs describing capabilities like 'generates', 'creates', 'analyzes', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no capabilities listed) and 'when should Claude use it' (no explicit use cases or scenarios). The 'Triggers on' line is not a proper 'Use when...' clause with meaningful context. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'security policy generator' repeated twice, which is redundant and unlikely to match natural user language. Missing common variations like 'security policies', 'compliance', 'access control', 'policy template', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Security Policy Generator' is somewhat specific to a domain, the lack of detail about what types of security policies or contexts makes it potentially overlap with other security-related skills. The 'Security Advanced skill category' reference doesn't clarify boundaries. | 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 with no substantive content. It describes what a security policy generator skill should do but provides absolutely no actual guidance, examples, templates, or workflows for generating security policies. The content is entirely meta-description without any actionable instructions.
Suggestions
Add concrete security policy templates or examples (e.g., access control policy, incident response policy) with actual content Claude can use or adapt
Include a step-by-step workflow for generating policies: gather requirements → select framework (SOC2/GDPR/etc.) → generate draft → validate against compliance checklist → iterate
Provide specific code or configuration examples for common policy generation tasks, such as generating policy documents from templates or validating policies against compliance frameworks
Add references to detailed materials for specific compliance frameworks (SOC2, GDPR, HIPAA) with clear navigation structure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need explained. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no specific commands, and no actual instructions for generating security policies. The content only describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined whatsoever. There are no steps, no validation checkpoints, and no process for actually generating security policies. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to detailed materials, no links to policy templates, compliance frameworks, or examples that would be essential for a security policy generator. | 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
994edc4
- 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.