security-group-generator
Security Group Generator - Auto-activating skill for AWS Skills. Triggers on: security group generator, security group generator Part of the AWS Skills skill category.
39
Quality
7%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/security-group-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, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill, and the redundant trigger terms suggest a template was filled in without thought. The description fails on nearly all dimensions of the rubric.
Suggestions
Add specific actions the skill performs, e.g., 'Creates AWS security group configurations with inbound/outbound rules, CIDR blocks, and port specifications'
Include a 'Use when...' clause with natural trigger scenarios like 'Use when the user needs to configure EC2 firewall rules, define network access policies, or set up security groups for AWS resources'
Add varied trigger terms users might naturally say: 'AWS firewall', 'EC2 security', 'inbound rules', 'outbound rules', 'port access', 'CIDR configuration'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Security Group Generator') without describing any concrete actions. There are no verbs explaining what it actually does - no mention of creating, configuring, defining rules, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' clause just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('security group generator' listed twice) and overly narrow. Missing natural variations users might say like 'AWS security group', 'firewall rules', 'inbound/outbound rules', 'EC2 security', or 'network access control'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'security group' is fairly specific to AWS networking context, which provides some distinctiveness. However, the lack of detail about what aspects of security groups it handles could cause conflicts with other AWS-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a hollow template with no actionable content. It describes what a security group generator skill would do but provides zero actual guidance on generating security groups - no AWS CLI commands, no CloudFormation/Terraform examples, no port/CIDR configurations, and no security best practices. The content is entirely meta-description without substance.
Suggestions
Add executable code examples showing how to create security groups (AWS CLI, CloudFormation, or Terraform with specific port/CIDR configurations)
Include concrete security best practices (e.g., principle of least privilege, avoiding 0.0.0.0/0 for SSH, common port configurations for web servers)
Define a clear workflow: gather requirements → generate configuration → validate rules → apply with verification
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with specific, actionable guidance
| 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. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly but never shows how to actually generate a security group - no AWS CLI commands, CloudFormation templates, or Terraform examples. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. For a 'generator' skill, there should be clear steps for gathering requirements, generating the security group configuration, and validating the output. None of this exists. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with headers, but there are no references to detailed materials, examples, or related documentation. The structure exists but contains no substantive content to disclose. | 2 / 3 |
Total | 5 / 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
0c08951
- 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.