creating-api-gateway-stage

Creates an API Gateway stage with CloudWatch logging, X-Ray tracing, throttling, WAF integration, and IAM roles following AWS best practices. Use when deploying a REST API to different environments such as dev, test, or production.

Quality

80%

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/serverless-skills/creating-api-gateway-stage/SKILL.md

Quality

Content

72%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 overview that exemplifies progressive disclosure by delegating the detailed procedure to a single real reference file. The trade-off is reduced in-body actionability and workflow clarity, since the executable steps and validation checkpoints live in the reference rather than the SKILL.md body.

Suggestions

Add a brief inline validation or verification checkpoint in the body (e.g., a one-line 'Confirm the stage is reachable and logs are flowing before handing off') so the workflow surfaces a checkpoint without inlining the whole procedure.

Include one or two concrete executable snippets in the troubleshooting section (e.g., the aws CLI / call_aws incantation to check the log group or WAF ACL) to raise in-body actionability.

Optionally surface the reference procedure's key steps as a short numbered summary in the body so the multi-step sequence is legible without opening the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: a brief overview, a single delegated procedure pointer, and concise troubleshooting without explaining what API Gateway is or how AWS works.	5 / 5
Actionability	The main creation procedure is delegated to the reference with only 'follow the procedure exactly'; the troubleshooting section does give concrete checks (role permissions, log group existence, stage- and method-level logging) but provides no executable commands.	3 / 5
Workflow Clarity	The body offers a single directive to follow an external procedure rather than an in-body sequenced workflow, and no validation checkpoints are visible in the body for this non-trivial stage-deployment task; the cap for missing validation on impactful deployment operations holds it at 3.	3 / 5
Progressive Disclosure	A clean overview with one clearly signaled, one-level-deep reference (references/create-api-gateway-stage.md, verified present), plus well-organized Overview/Create/Troubleshooting sections for easy navigation.	5 / 5
	Total	16 / 20 Passed

Description

87%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 clearly answers both 'what' and 'when' with comprehensive capability coverage and an explicit trigger clause. Minor room to improve specificity and trigger-term breadth by adding more distinct action verbs and synonyms.

Dimension	Reasoning	Score
Specificity	Lists five concrete capabilities (CloudWatch logging, X-Ray tracing, throttling, WAF integration, IAM roles), but the single primary action verb 'Creates an API Gateway stage with…' stops just short of the multiple-distinct-actions anchor at 5.	4 / 5
Completeness	Explicitly states what it does (creates a stage with logging, tracing, throttling, WAF, IAM roles) and when to use it via a concrete 'Use when deploying a REST API to different environments such as dev, test, or production' trigger clause.	5 / 5
Trigger Term Quality	Natural terms 'API Gateway stage', 'REST API', 'deploying', and 'dev, test, or production' give good keyword coverage a user would say, though a few synonyms (e.g., 'API deployment', environment variants) are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a narrow AWS-specific niche (API Gateway stage creation) with distinct triggers, making overlap with other skills minimal.	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/creating-api-gateway-stage/SKILL.md
Commit: d6ad2e4

Reviewed: about 2 hours 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.