api-gateway

AWS API Gateway for REST and HTTP API management. Use when creating APIs, configuring integrations, setting up authorization, managing stages, implementing rate limiting, or troubleshooting API issues.

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/api-gateway/SKILL.md

Quality

Content

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

The body is a dense, actionable reference with strong executable examples and good section organization. Its main weaknesses are redundant CLI reference tables and basic concept definitions that hurt conciseness, and missing validation checkpoints in the deployment workflow.

Suggestions

Remove or collapse the CLI Reference tables that duplicate commands already shown in Common Patterns, or move them to a separate reference file to reduce redundancy.

Add validation checkpoints to the deployment workflow (e.g. `aws apigatewayv2 get-api` / `get-deployment` to verify, or a test-invoke step) before treating the API as live in prod.

Trim the 'Key Components' definitions (Resources, Methods, Integrations, Stages) that restate concepts Claude already knows, keeping only API-Gateway-specific nuance.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tables and code blocks, but the CLI Reference section re-lists commands already demonstrated in Common Patterns and the 'Key Components' block defines basic concepts (resources, methods, stages) Claude already knows, so it could be tightened.	3 / 5
Actionability	Provides copy-paste-ready AWS CLI commands, a SAM template, and a Python handler covering the common cases (HTTP API, REST API, CORS, JWT authorizer), matching the fully-executable anchor.	5 / 5
Workflow Clarity	The REST API creation sequence (create-api → get-resources → create-resource → put-method → put-integration → create-deployment) is clearly ordered, but there are no validation checkpoints (e.g. test endpoint, verify deployment), and deploying to a prod stage without verification caps this at 3 per the destructive/deploy guidance.	3 / 5
Progressive Disclosure	Well-organized single-file structure with a Table of Contents and clear section headers (Core Concepts, Common Patterns, CLI Reference, Best Practices, Troubleshooting, References) giving easy navigation, though everything is inline with no one-level-deep bundle references, keeping it below 5.	4 / 5
	Total	15 / 20 Passed

Description

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

The description is strong: it names the service, lists six concrete capabilities, and provides an explicit 'Use when' trigger clause. Trigger terms and distinctiveness are good rather than perfect, with a few common synonyms missing and minor overlap risk against adjacent AWS skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creating APIs, configuring integrations, setting up authorization, managing stages, implementing rate limiting, or troubleshooting API issues' — giving comprehensive coverage of API Gateway capabilities, matching the anchor for multiple specific concrete actions.	5 / 5
Completeness	Explicitly states both what ('AWS API Gateway for REST and HTTP API management') and when ('Use when creating APIs, configuring integrations...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Good natural-term coverage ('creating APIs', 'rate limiting', 'authorization', 'stages', 'troubleshooting') that users would say, but a few common phrases (e.g. CORS, throttling) are absent, so it falls short of the comprehensive-synonym anchor at 5.	4 / 5
Distinctiveness Conflict Risk	API Gateway is a clear niche with distinct triggers (stages, rate limiting, integrations), but there is minor overlap risk with closely related AWS skills (e.g. Lambda, AppSync), so it sits below the minimal-conflict anchor at 5.	4 / 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: itsmostafa/aws-agent-skills
Path: skills/api-gateway/SKILL.md
Commit: e786d25

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