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.
36
3%
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 extremely weak across all dimensions. It provides no concrete actions, repeats the same trigger term, lacks a 'Use when...' clause, and reads more like a label than a functional description. It would be nearly useless for Claude to differentiate this skill from other AWS-related skills in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates AWS security group configurations with inbound and outbound rules, produces CloudFormation or Terraform templates for security groups, and validates CIDR ranges and port configurations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about creating or configuring AWS security groups, firewall rules, inbound/outbound rules, VPC security, SG rules, or port access policies.'
Remove the redundant duplicate trigger term ('security group generator' listed twice) and expand with natural variations users would actually say, such as 'AWS SG', 'security group rules', 'EC2 firewall', 'port access', 'CIDR block rules'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Security Group Generator', 'AWS Skills') but does not describe any concrete actions. There is no mention of what the skill actually does—e.g., creating security group rules, configuring inbound/outbound rules, generating CloudFormation templates, etc. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no explanation of capabilities and no explicit 'Use when...' clause—only a redundant trigger line that doesn't serve as meaningful guidance. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'security group generator' repeated twice. It misses natural variations users would say such as 'security group', 'AWS security group', 'firewall rules', 'inbound rules', 'outbound rules', 'SG', 'VPC security', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Security Group Generator' and 'AWS Skills' provides some specificity to a niche, but the lack of concrete actions or detailed triggers means it could overlap with other AWS-related skills. It's somewhat distinguishable due to the 'security group' keyword but not clearly scoped. | 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 an empty shell with no substantive content. It describes what it would do in abstract terms but provides zero actionable guidance for generating AWS security groups—no code examples, no CLI commands, no CloudFormation templates, no ingress/egress rule patterns, and no validation steps. It reads like a placeholder template that was never filled in.
Suggestions
Add concrete, executable examples such as AWS CLI commands (`aws ec2 create-security-group`), CloudFormation YAML snippets, or Terraform HCL blocks for creating security groups with common rule patterns (e.g., web server, database, bastion host).
Define a clear workflow: 1) Gather requirements (ports, protocols, CIDR ranges), 2) Generate the security group definition, 3) Validate rules against least-privilege principles, 4) Apply and verify.
Include specific security best practices as actionable constraints, e.g., 'Never allow 0.0.0.0/0 on port 22 unless explicitly requested; suggest bastion host pattern instead.'
Remove all generic filler text ('Provides step-by-step guidance', 'Follows industry best practices') and replace with actual guidance and code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler text that provides no actionable information. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty platitudes. The entire skill explains what it does without ever doing it. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no AWS CLI examples, no CloudFormation/Terraform snippets, no security group rule definitions. It only describes capabilities abstractly without providing any executable or specific instructions. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps. There are no validation checkpoints or sequenced operations. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no separation of overview from detailed content. There are no bundle files to reference either. | 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
3a2d27d
- 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.