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

86%

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

72%

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

A well-disclosed, concise overview that correctly delegates detail to a real one-level reference, but the body itself is light on executable guidance and does not surface the workflow sequence or its validation checkpoints inline.

Suggestions

Add a short numbered step summary (e.g. create API → resource → method → integration → permissions → deploy → test) in the body so the workflow sequence and its validation checkpoints are visible without opening the reference.

Include at least one copy-paste-ready snippet in the body — e.g. the Lambda proxy response shape or the aws lambda add-permission command — to raise actionability beyond pointers.

State the explicit validation gate (verify Lambda proxy response format and invoke the deployed endpoint) inline so destructive deployment steps have a visible feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what API Gateway or Lambda is, and every section earns its tokens by either routing to the procedure or giving terse troubleshooting pointers.	3 / 3
Actionability	It names concrete options ('AWS_IAM', 'COGNITO_USER_POOLS', 'lambda:InvokeFunction', 'enable_cors') but offers no executable commands or code in the body itself, deferring all steps to the reference, so guidance is incomplete inline.	2 / 3
Workflow Clarity	The body signals 'follow the procedure exactly' and links the reference, but the step sequence and validation checkpoints (verify response format, test integration) live only in the reference rather than being surfaced in the body.	2 / 3
Progressive Disclosure	A clean overview that points to a single well-signaled, one-level-deep reference (verified real and self-contained with no nested references), with content appropriately split between SKILL.md and the reference.	3 / 3
	Total	10 / 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.

A strong description: third-person, concrete, and explicit about both capability and trigger conditions, with a distinct, low-conflict niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creating a REST or HTTP API with resource/method setup, Lambda proxy integration, permissions, and deployment' plus CORS, throttling, and access logging — rather than vague language.	3 / 3
Completeness	Explicitly answers what it does (creates/deploys the API wiring) and when to use it via 'Always use this skill when connecting Lambda to API Gateway', satisfying both halves.	3 / 3
Trigger Term Quality	Uses natural terms a user would say ('AWS Lambda', 'Amazon API Gateway', 'connecting Lambda to API Gateway') with good coverage of the phrasings users actually employ.	3 / 3
Distinctiveness Conflict Risk	The Lambda-to-API-Gateway connection niche is specific and paired 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/serverless-skills/connecting-lambda-to-api-gateway/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.