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

78%

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

57%

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

The body is a well-structured, lean overview that correctly offloads a long procedure to a single one-level-deep reference with clean navigation. Its weaknesses are minor inline redundancy and the fact that the executable procedure and validation checkpoints live in the reference rather than the body.

Suggestions

Consolidate the repeated resource-component enumeration so it appears once (e.g., drop it from the Overview or the 'Create a production VPC' intro) to tighten conciseness.

Add a brief inline summary of the procedure's key sequence and its validation checkpoint (e.g., 'the procedure validates AZ count up front and runs a final VPC validation before reporting success') so the workflow is visible without opening the reference.

Consider including one short copy-paste example of an actual call_aws command for a representative step to lift actionability beyond the parameter spec.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no concept-explanation padding, but the component list (subnets, internet gateway, NAT gateways, route tables, security groups) is restated in both the Overview and the 'Create a production VPC' intro, so it could be tightened.	2 / 3
Actionability	Provides a concrete parameter list with required/optional/defaults and one real command ('aws ec2 describe-availability-zones'), but the core creation procedure is delegated to the reference rather than being executable from the body itself.	2 / 3
Workflow Clarity	The body delegates the multi-step sequence to the referenced procedure ('follow the procedure exactly') and the troubleshooting section offers error-recovery hints, but the sequence and validation checkpoints are not presented inline in the body.	2 / 3
Progressive Disclosure	A clear overview points to a single, well-signaled, verified one-level-deep reference (references/create-production-vpc-multi-az.md) with no nested references, and content is appropriately split between the body and the reference.	3 / 3
	Total	9 / 12 Passed

Description

100%

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 specific, trigger-rich, and complete with an explicit 'Use when' clause, clearly distinguishing this skill within a narrow AWS-infrastructure niche. It is concise without padding or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete resources ('public and private subnets', 'internet gateway, NAT gateways, route tables, and security groups') rather than vague language, matching the score-3 anchor.	3 / 3
Completeness	Clearly answers what it does (creates a production-ready VPC with the listed components) and when to use it via an explicit 'Use when...' clause, matching the score-3 anchor.	3 / 3
Trigger Term Quality	'Use when deploying multi-AZ VPC infrastructure with automatic CIDR planning and DNS resolution' provides good coverage of the natural terms an AWS user would say (multi-AZ VPC, subnets, NAT gateways, CIDR, DNS).	3 / 3
Distinctiveness Conflict Risk	Occupies a clear, specific niche (production multi-AZ AWS VPC creation) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: 222ce56

Reviewed: 3 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.