creating-production-vpc-multi-az

Creates a production-ready VPC with public and private subnets across multiple Availability Zones, including internet gateway, NAT gateways, route tables, and security groups following AWS Well-Architected principles. Use when deploying multi-AZ VPC infrastructure with automatic CIDR planning and DNS resolution.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured overview skill: concise, concrete parameters, effective one-level-deep delegation to a complete procedural reference with validation steps, and useful inline troubleshooting. The only notable improvement is trimming the Overview paragraph that restates the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The body is lean — a compact parameter list and terse troubleshooting entries with no explanation of concepts Claude already knows — but the Overview paragraph ("Covers VPC creation with DNS support, public and private subnet layout...") nearly duplicates the frontmatter description and could be trimmed.	4 / 5
Actionability	Key parameters are fully concrete (names, defaults, ranges like "default 3): Number of AZs (2–6)"), troubleshooting includes an executable command ("aws ec2 describe-availability-zones"), and the full executable procedure is one clearly signaled link away; the body itself carries few commands, which keeps it just below fully copy-paste-ready.	4 / 5
Workflow Clarity	The multi-step process is delegated to the referenced procedure, which contains a sequenced 12-step workflow with explicit validation checkpoints ("Validate Region and Get Available Availability Zones", "Validate VPC Configuration") and constraints; the body's own troubleshooting section covers failure recovery, but the body alone does not surface the validation checkpoints, leaving a minor gap.	4 / 5
Progressive Disclosure	The body is a genuine overview: quick-answer material (parameters, troubleshooting) stays inline, the full procedure lives in a single well-signaled one-level-deep reference ([references/create-production-vpc-multi-az.md](references/create-production-vpc-multi-az.md)) that exists and itself contains no nested references.	5 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: specific, third-person, comprehensive in capability coverage, and paired with an explicit and concrete "Use when..." trigger clause. Its only minor gap is thin synonym coverage for natural user phrasings.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete components and actions — "public and private subnets across multiple Availability Zones, including internet gateway, NAT gateways, route tables, and security groups" — in third-person voice, giving comprehensive coverage of what the skill builds.	5 / 5
Completeness	Explicitly answers both questions: the "what" is the full component list, and the "when" is a concrete trigger clause — "Use when deploying multi-AZ VPC infrastructure with automatic CIDR planning and DNS resolution."	5 / 5
Trigger Term Quality	Strong natural keywords users would say ("VPC", "multi-AZ", "Availability Zones", "NAT gateways", "CIDR", "DNS"), but a few common synonyms a user might naturally use (e.g. "AWS networking", "private network setup", "subnets") are absent, so it falls just short of the comprehensive-synonyms anchor.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (production multi-AZ VPC creation) with distinct triggers (multi-AZ, NAT gateways, CIDR planning) that would not naturally collide with unrelated infrastructure skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: aws/agent-toolkit-for-aws
Path: skills/specialized-skills/networking-and-content-delivery-skills/creating-production-vpc-multi-az/SKILL.md
Commit: b8171ad

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.