vpc-network-designer
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill vpc-network-designerVpc Network Designer - Auto-activating skill for AWS Skills. Triggers on: vpc network designer, vpc network designer 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, consisting only of the skill name repeated as trigger terms with no actual capability description. It fails to explain what VPC design actions the skill performs and provides no guidance on when Claude should select it. The description would be nearly useless for skill selection among multiple AWS-related skills.
Suggestions
Add specific concrete actions the skill performs, such as 'Designs AWS VPC architectures, configures subnets and CIDR blocks, sets up route tables, creates security groups and NACLs'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user needs to design AWS network infrastructure, create VPCs, configure subnets, or plan cloud network topology'
Add common user terminology variations: 'virtual private cloud', 'AWS networking', 'subnet design', 'network segmentation', 'cloud network architecture'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the skill name 'Vpc Network Designer' repeated. There's no explanation of what the skill actually does (e.g., design VPCs, configure subnets, set up routing tables). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when to use' guidance. There's no explicit trigger clause or use case explanation. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('vpc network designer, vpc network designer'). Missing natural user terms like 'AWS VPC', 'virtual private cloud', 'subnets', 'network architecture', 'CIDR blocks'. | 1 / 3 |
Distinctiveness Conflict Risk | The 'VPC' and 'AWS' terms provide some specificity to distinguish from generic networking skills, but without concrete actions, it could still conflict with other AWS networking-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual VPC network design content. It contains only generic placeholder text that could apply to any skill topic. There is no actionable guidance, no AWS-specific information, and no value added beyond what the skill title already conveys.
Suggestions
Add concrete VPC design examples with CIDR blocks, subnet configurations, and AWS CLI or CloudFormation/Terraform code snippets
Define a clear workflow for VPC design: requirements gathering → CIDR planning → subnet layout → route tables → security groups → validation
Include specific guidance on common patterns (public/private subnets, NAT gateways, VPC peering, transit gateways) with executable examples
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about VPC network design. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no code, no commands, no specific VPC configurations, CIDR blocks, subnet layouts, or AWS CLI examples. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is defined. VPC design involves multiple steps (CIDR planning, subnet creation, route tables, NAT gateways, security groups) but none are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no links to AWS-specific resources, and no organization of VPC topics (public/private subnets, peering, transit gateways, etc.). | 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
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.