Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill security-group-generatorSecurity Group Generator - Auto-activating skill for AWS Skills. Triggers on: security group generator, security group generator Part of the AWS Skills skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped - it's essentially just a title with redundant trigger terms and category metadata. It provides no information about what the skill actually does (create security groups? modify them? generate templates?) and offers no meaningful guidance for when Claude should select it over other skills.
Suggestions
Add specific actions the skill performs, e.g., 'Creates AWS EC2 security groups with ingress/egress rules, configures port access, and generates CloudFormation templates for security group definitions.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user needs to create firewall rules, configure EC2 network access, set up VPC security groups, or manage inbound/outbound traffic rules in AWS.'
Include common user phrases and file types: 'AWS security group', 'firewall rules', 'port 443', 'SSH access', 'ingress rules', 'CloudFormation security'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Security Group Generator') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of creating rules, configuring ports, managing ingress/egress, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just a circular reference to the skill name. There's no explicit 'Use when...' clause with meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('security group generator' listed twice) and miss natural variations users would say like 'AWS security group', 'firewall rules', 'EC2 security', 'inbound rules', 'outbound rules', or 'VPC security'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'AWS' and 'security group' provides some specificity to AWS infrastructure, but without describing actual capabilities, it could conflict with other AWS-related skills or general security skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template that provides no actual guidance for generating AWS security groups. It contains only generic boilerplate text that describes capabilities without demonstrating them. A security group generator skill should include concrete examples of security group configurations, CLI commands or IaC templates, and guidance on security best practices like least-privilege access.
Suggestions
Add executable code examples showing how to create security groups (AWS CLI, CloudFormation, or Terraform templates with common patterns like web server, database, or bastion host configurations)
Include a workflow with validation steps: define ingress/egress rules -> validate against least-privilege principles -> apply and verify
Provide concrete security group rule examples with specific ports, protocols, and CIDR ranges for common use cases
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actionable content
| 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 is defined at all. For a security group generator, there should be clear steps: define rules, specify ports/protocols, validate against least-privilege principles, etc. None of this is present. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no meaningful structure. No references to detailed documentation, examples, or related resources that would help with actual security group generation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
Table of Contents
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.