connecting-lambda-to-api-gateway

Connects an existing AWS Lambda function to Amazon API Gateway by creating a REST or HTTP API with resource/method setup, Lambda proxy integration, permissions, and deployment. Always use this skill when connecting Lambda to API Gateway — it handles CORS, throttling, access logging, and production security hardening that are easy to miss.

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

86%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.

An exemplary progressive-disclosure body: a lean overview that delegates the full procedure to a single well-organized reference file and keeps a concise, specific troubleshooting section inline. Adding a brief step summary or an inline validation cue in the body would make the workflow fully self-evident at a glance.

Dimension	Reasoning	Score
Conciseness	The ~30-line body is lean and assumes Claude's competence: no explanation of what Lambda or API Gateway is, no padding, and every section (overview, procedure pointer, troubleshooting) earns its tokens.	5 / 5
Actionability	'follow the procedure exactly' links to a real reference file containing concrete commands (e.g., `aws lambda get-function`), and troubleshooting gives specific checks ('Verify `enable_cors` was set to true, the OPTIONS method was created'). Not a 5 because the body itself contains no inline command or example, deferring all executable detail to the reference.	4 / 5
Workflow Clarity	The directive is unambiguous ('To create a REST API and wire it to a Lambda function, follow the procedure exactly') and delegates to a procedure whose steps include validation checkpoints (verify dependencies, validate the Lambda exists, abort conditions). Not a 5 because the body surfaces no step summary or validation cue inline.	4 / 5
Progressive Disclosure	A clear overview with a well-signaled one-level-deep markdown link to references/lambda-gateway-api.md (a real 260-line file with no nested references); content is appropriately split and navigation is easy.	5 / 5
	Total	18 / 20 Passed

Description

83%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 third-person description that concretely enumerates its capabilities and includes an explicit use-when clause with a rationale. Its only weakness is a single narrow trigger phrase; adding common user phrasings (e.g., 'expose a Lambda over HTTP', 'create an API endpoint') would broaden triggering.

Suggestions

Expand the when-clause with additional trigger variations such as 'expose a Lambda function over HTTP', 'create an API endpoint for a Lambda', or 'invoke Lambda via REST/HTTP API'.

Include a few natural synonyms in the capability list (e.g., 'API routes', 'endpoint', 'invoke') so users phrasing the task differently still match.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'creating a REST or HTTP API with resource/method setup, Lambda proxy integration, permissions, and deployment' plus 'CORS, throttling, access logging, and production security hardening' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Both what ('creating a REST or HTTP API with resource/method setup, Lambda proxy integration, permissions, and deployment') and when ('Always use this skill when connecting Lambda to API Gateway') are explicitly answered. Not a 5 because the when-clause offers only a single trigger phrase rather than several concrete trigger variations.	4 / 5
Trigger Term Quality	'connecting Lambda to API Gateway', 'REST or HTTP API', 'CORS', and 'throttling' are natural phrases users would say, but coverage stops at the core phrase without synonyms like 'expose a Lambda over HTTP' or 'create an API endpoint for a function'.	4 / 5
Distinctiveness Conflict Risk	The Lambda-to-API-Gateway wiring niche is clearly distinct with an unambiguous trigger ('connecting Lambda to API Gateway'), creating minimal conflict risk with adjacent AWS skills.	5 / 5
	Total	18 / 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/serverless-skills/connecting-lambda-to-api-gateway/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.