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

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/specialized-skills/networking-and-content-delivery-skills/creating-production-vpc-multi-az/SKILL.md

Quality

Content

61%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, concise overview that uses progressive disclosure effectively to point to a detailed procedure. Its weaknesses are that the body carries no executable guidance or validation checkpoints on its own, relying entirely on the referenced procedure for actionability and workflow safety.

Suggestions

Add at least one inline validation checkpoint or a brief note that the procedure ends with a validation step, so destructive infrastructure provisioning shows an explicit feedback loop in the body.

Include one or two concrete example AWS CLI commands inline (e.g., the AZ verification or VPC creation call) so the body is actionable without opening the reference.

Surface the key procedural steps (e.g., a numbered 3–4 step summary) in the body so the workflow sequence is legible before delegating to the reference file.

Dimension	Reasoning	Score
Conciseness	The body is lean—an overview, parameter list, one reference link, and concise troubleshooting—and largely assumes competence; the only mild trim opportunity is the troubleshooting section restating procedure behavior, which keeps it just below the 'lean and efficient' top anchor.	4 / 5
Actionability	The body itself gives no executable commands—it only lists parameters and delegates execution to the reference file—so concrete guidance is indirect rather than copy-paste ready, fitting the 'some concrete guidance but incomplete' anchor.	3 / 5
Workflow Clarity	The body names phases and points to the procedure, and the reference file does include a final 'Validate VPC Configuration' step, but the SKILL.md body surfaces no explicit validation checkpoint and just says 'follow the procedure exactly'; per the destructive/batch cap guidance, an infrastructure-provisioning skill without visible validation in the body caps at 3.	3 / 5
Progressive Disclosure	The SKILL.md is a concise overview pointing to one real, one-level-deep reference (references/create-production-vpc-multi-az.md, verified to exist) with a clearly signaled link, and inlining only parameters and troubleshooting; minor gap is no section navigation beyond the single pointer.	4 / 5
	Total	14 / 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.

A strong, specific description that clearly states both capabilities and trigger conditions in third person, with concrete resource types and AWS Well-Architected framing. The only minor gap is keyword coverage leaning somewhat on AWS jargon rather than user-natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions—'public and private subnets', 'internet gateway, NAT gateways, route tables, and security groups', 'automatic CIDR planning and DNS resolution'—with comprehensive coverage, matching the 'Lists multiple specific concrete actions' anchor.	5 / 5
Completeness	Explicitly answers 'what' ('Creates a production-ready VPC with...') and 'when' ('Use when deploying multi-AZ VPC infrastructure...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural terms like 'deploying multi-AZ VPC infrastructure' and 'production-ready VPC' are present, but it leans on AWS jargon and omits common synonyms a user might say (e.g., 'set up', 'network', 'private network'); good but not comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	A clear niche—production multi-AZ VPC with NAT/route tables/CIDR planning—that is unlikely to trigger for unrelated skills, with distinct, specific triggers and minimal conflict risk.	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: 8ea26bd

Reviewed: 1 day 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.