enabling-lambda-vpc-internet-access

Enables internet access for AWS Lambda functions deployed in VPC subnets by creating NAT Gateway infrastructure, configuring public/private subnet routing, and updating security groups. Use when a VPC-attached Lambda function cannot reach the internet.

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/enabling-lambda-vpc-internet-access/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 content is well-structured with excellent progressive disclosure, but the body delegates the actionable procedure and workflow to the reference while re-explaining a known concept, leaving its own actionability and workflow clarity at a mid level. It works well as a hub but offers limited standalone executable guidance.

Suggestions

Trim the Overview's restatement of how VPC Lambda internet access works; Claude already knows this and the description already conveys the purpose.

Add a short inline summary of the high-level procedure steps (e.g., create NAT Gateway in public subnet, add 0.0.0.0/0 route to private route table, verify SG egress) so the body is actionable without opening the reference.

Surface at least one validation checkpoint in the body (e.g., 'After route table changes, confirm the 0.0.0.0/0 target is the NAT Gateway before testing') to strengthen workflow clarity for this infrastructure-changing task.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and well-organized, but the Overview re-explains a concept Claude already knows ('Lambda functions in a VPC cannot receive public IP addresses, so outbound internet access requires NAT Gateway infrastructure...'), which is mild padding.	2 / 3
Actionability	Troubleshooting offers concrete checks ('Verify the route table... has a 0.0.0.0/0 route', 'Check that security group outbound rules allow the necessary ports'), but the core procedure is delegated to the reference with no executable commands in the body itself.	2 / 3
Workflow Clarity	The body points to the reference for the multi-step sequence ('follow the procedure exactly. See [reference]') without showing steps or validation checkpoints inline, leaving the workflow sequence and verification implicit in the body.	2 / 3
Progressive Disclosure	A clear overview in SKILL.md links to one real, one-level-deep reference (references/lambda-vpc-internet-access.md) with a well-signaled markdown link and well-organized sections including troubleshooting subsections.	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 concise, specific, and complete, answering both what the skill does and when to use it with natural trigger language and a distinct niche. It reads as a strong model example with no significant weaknesses.

Dimension	Reasoning	Score
Specificity	Names three concrete actions — 'creating NAT Gateway infrastructure', 'configuring public/private subnet routing', and 'updating security groups' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Clearly states what it does (enables internet access via NAT/routing/security groups) and gives an explicit 'Use when a VPC-attached Lambda function cannot reach the internet' trigger clause.	3 / 3
Trigger Term Quality	Uses natural terms a user would say ('AWS Lambda', 'VPC', 'NAT Gateway', 'internet access', 'cannot reach the internet') with good coverage rather than obscure jargon.	3 / 3
Distinctiveness Conflict Risk	Targets a narrow, well-defined niche (VPC Lambda outbound internet via NAT Gateway) with distinct triggers, making overlap with unrelated skills unlikely.	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/enabling-lambda-vpc-internet-access/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.