connecting-vpcs-with-peering

Establishes VPC peering connections between two VPCs for direct private network connectivity. Always use this skill when creating or managing VPC peering — it validates CIDR overlap, updates all route tables in both VPCs, configures DNS resolution, and provides security group guidance that are critical for correct connectivity.

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/connecting-vpcs-with-peering/SKILL.md

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, token-efficient SKILL.md that delegates the full procedure to a single real, one-level-deep reference and keeps genuinely useful troubleshooting guidance inline. The only soft spot is that the body itself contains no executable commands, relying entirely on the referenced SOP for step-by-step execution.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude knows VPC peering, and keeps troubleshooting to one-liners ("Replace existing routes instead of creating new ones"); it is not 5 because the Overview and the summary paragraph "It validates both VPCs exist, checks for CIDR overlap..." duplicate each other and the description, and "follow the procedure exactly" is filler.	4 / 5
Actionability	Though the body carries no code, per the instruction-skill note that is not penalized when guidance is actionable: it points to a real, complete procedure file, states required inputs ("requires the requester and accepter VPC IDs at minimum"), and gives concrete fixes ("Both VPCs must have DNS resolution and DNS hostnames enabled in their VPC settings"); not 5 because all executable commands live in the reference rather than the body.	4 / 5
Workflow Clarity	The lifecycle (validate, create, accept, route, DNS) is delegated to a well-sequenced SOP with validation checkpoints, and the troubleshooting section provides error-recovery feedback (pending state, route failure, DNS failure); not 5 because the body's own sequence is prose with checkpoints only in the reference, and not 3 because sequence and validation are both present and clearly signaled.	4 / 5
Progressive Disclosure	Verified against the actual bundle: exactly one reference file, well-signaled in a dedicated section ("See [VPC peering connection procedure](references/vpc-peering-connection.md)"), one level deep with no nested references, and appropriately concise overview and troubleshooting inlined — matching the clear-overview anchor.	5 / 5
	Total	17 / 20 Passed

Description

75%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 description that pairs a concrete multi-action 'what' with an explicit 'use when' trigger and domain-specific keywords. It is held just below top marks by trigger phrases that restate the domain rather than diversify, and by a niche that sits near related VPC-connectivity skills.

Dimension	Reasoning	Score
Specificity	"validates CIDR overlap, updates all route tables in both VPCs, configures DNS resolution, and provides security group guidance" lists several specific concrete actions, matching the 'minor gaps' anchor; it is not 5 because accepting the connection and cross-account/cross-region scenarios are unmentioned, and not 3 because it goes well beyond 1-2 actions.	4 / 5
Completeness	It explicitly answers both what ("Establishes VPC peering connections... validates CIDR overlap...") and when ("Always use this skill when creating or managing VPC peering"); not 5 because the when-clause restates the domain name rather than adding distinct concrete trigger phrases, and not 3 because the when is explicitly stated rather than only implied.	4 / 5
Trigger Term Quality	Natural terms like "VPC peering", "creating or managing VPC peering", "CIDR overlap", "route tables", and "DNS resolution" give good keyword coverage; it falls short of 5 because common user phrasings such as "peer two VPCs" or "connect VPCs privately" are missing, and exceeds 3 because coverage is not limited to a single generic keyword.	4 / 5
Distinctiveness Conflict Risk	"VPC peering connections between two VPCs for direct private network connectivity" carves out a clear, distinct niche; not 5 because a user asking to connect two VPCs could plausibly want Transit Gateway, VPN, or PrivateLink, creating minor overlap risk with closely related networking skills.	4 / 5
	Total	16 / 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/connecting-vpcs-with-peering/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.