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
Quality
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 severely underdeveloped, consisting primarily of the skill name repeated as trigger terms with no actual description of capabilities. It fails to explain what the skill does, what actions it can perform, or provide meaningful guidance for when Claude should select it over other skills.
Suggestions
Add specific capabilities: 'Designs and configures AWS VPC architectures including subnets, route tables, internet gateways, NAT gateways, and security groups.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user needs to create VPC infrastructure, configure AWS networking, set up subnets, or design cloud network architecture.'
Add common user language variations: 'VPC', 'virtual private cloud', 'AWS network', 'subnet design', 'network topology', 'CIDR blocks'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'VPC Network Designer' is just a name, not a description of capabilities. There's no indication of what this skill actually does (e.g., creates VPCs, configures subnets, sets up routing tables). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just the skill name repeated. There's no explicit guidance on when Claude should select this skill or what user requests would trigger it. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'vpc network designer' repeated twice, which is the skill name itself rather than natural user language. Missing obvious terms like 'VPC', 'subnet', 'network architecture', 'AWS networking', 'CIDR', 'security groups', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'VPC Network Designer' is somewhat specific to AWS VPC work, the lack of detail means it could conflict with other AWS networking skills. The mention of 'AWS Skills' category provides some context but insufficient differentiation. | 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 that provides no actual VPC network design guidance. It contains only generic boilerplate about 'automated assistance' and 'best practices' without any concrete information about CIDR blocks, subnet design, routing tables, security groups, NAT gateways, or any other VPC concepts. The skill would be completely useless for actually helping design AWS VPC networks.
Suggestions
Add concrete VPC design examples with actual CIDR blocks, subnet layouts, and CloudFormation/Terraform code snippets
Include a step-by-step workflow for VPC design: requirements gathering → CIDR planning → subnet allocation → routing → security groups → validation
Provide specific guidance on common VPC patterns (public/private subnets, multi-AZ, hub-and-spoke) with executable infrastructure-as-code examples
Add validation checkpoints such as CIDR overlap checks, route table verification, and security group rule auditing
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual VPC design guidance. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or specific VPC design patterns are provided. The content describes what the skill does abstractly but gives zero executable guidance on actually designing VPC networks. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for designing a VPC, no CIDR planning guidance, no subnet layout instructions, and no validation checkpoints for network configurations. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no references to detailed materials, no links to architecture patterns, and no structured navigation to VPC-specific documentation. | 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
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.