vpc-network-designer
Vpc Network Designer - Auto-activating skill for AWS Skills. Triggers on: vpc network designer, vpc network designer 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/vpc-network-designer/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 essentially a placeholder that repeats the skill name without providing any meaningful information about what the skill does or when it should be used. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it nearly impossible for Claude to reliably select this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Designs and configures AWS VPC architectures including subnets, route tables, NAT gateways, internet gateways, and security groups.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about VPC design, AWS networking, subnet planning, CIDR blocks, network ACLs, or cloud network architecture.'
Remove the duplicate trigger term 'vpc network designer' and replace with diverse natural language variations users would actually say, such as 'AWS network setup', 'create a VPC', 'subnet layout', 'network topology'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. 'Vpc Network Designer' is a name, not a description of capabilities. There are no specific actions like 'creates VPCs', 'configures subnets', 'sets up route tables', 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 meaningful 'Use when...' guidance beyond the skill name itself. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'vpc network designer' repeated twice. It misses natural user terms like 'VPC', 'subnet', 'network architecture', 'CIDR', 'security groups', 'AWS networking', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'VPC' and 'network designer' provides some domain specificity within AWS, but the lack of concrete actions means it could overlap with other AWS networking skills. The 'AWS Skills' category label helps slightly. | 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 template with no substantive content. It contains only boilerplate metadata-like descriptions that repeat the skill name without providing any actual guidance on VPC network design — no CIDR planning, subnet strategies, routing tables, NAT gateways, security groups, NACLs, or any AWS networking concepts. It is entirely non-functional as a skill.
Suggestions
Add concrete, executable content such as CloudFormation/Terraform templates for common VPC architectures (e.g., public/private subnet layout, multi-AZ design).
Include a clear workflow with steps: define CIDR ranges → create subnets → configure route tables → set up NAT/IGW → apply security groups/NACLs, with validation at each stage.
Provide specific examples of VPC designs (e.g., 3-tier web app, isolated workloads) with actual IP ranges, subnet sizes, and AWS CLI or IaC code.
Remove all boilerplate filler text ('This skill provides automated assistance...') and replace with actionable technical guidance that Claude doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'vpc network designer' excessively, and contains zero substantive technical content about VPC design. | 1 / 3 |
Actionability | There are no concrete instructions, code examples, commands, 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 sequences, no validation checkpoints — just generic claims about capabilities without any actual process. | 1 / 3 |
Progressive Disclosure | No bundle files exist, no references to external resources, and the content is a monolithic block of placeholder text with no meaningful structure or navigation to deeper content. | 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.