Name: amazon-api-gateway
Rating: 55.2 (1 reviews)
Author: membranedev

amazon-api-gateway

Amazon API Gateway integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amazon API Gateway data.

Quality

62%

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

Quality

Content

67%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 highly actionable with concrete Membrane CLI commands and a strong, checkpoint-driven connection workflow. Its main weaknesses are an unnecessary introductory paragraph that over-explains API Gateway and small structural/labeling gaps in the workflow steps.

Suggestions

Remove or drastically shorten the opening paragraph explaining what Amazon API Gateway is; Claude already knows this and it is padding.

Fix the broken step labeling: label the first connection step '1a' (or remove the '1b'/'Step 2' references) so the sequence is unambiguous.

Add a brief verification/confirmation step after running actions or issuing proxy requests (especially for mutating methods like DELETE), and either populate 'Popular actions' with real examples or remove that heading.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ('Amazon API Gateway is a fully managed service that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale') explains a concept Claude already knows, and 'so you can focus on the integration logic rather than auth plumbing' is marketing-flavored padding, though the command-focused sections are mostly efficient.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request with a full flag table) with obvious placeholders, but the 'Popular actions' heading merely repeats the discovery command without enumerating actual popular actions.	4 / 5
Workflow Clarity	The connection workflow has explicit checkpoints and a feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR handling with re-polling), but it references an unlabeled 'Step 2' and a '1b' with no '1a', and offers no verification for potentially destructive proxy operations (DELETE).	4 / 5
Progressive Disclosure	With no bundle files present, the skill is self-contained and well-sectioned with clear headers, though the detailed connection state-machine and the proxy flag reference table are inline content that could plausibly live in separate reference files.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly uses third-person voice and includes an explicit 'Use when' trigger, giving it solid completeness and distinctiveness. It is weakened by vague, non-concrete capability language ('manage data, records, automate workflows') and a lack of trigger-term synonyms.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete API Gateway operations such as creating and deploying APIs, managing resources and methods, and configuring stages.

Expand trigger terms to include natural synonyms users say, e.g. 'REST API', 'API endpoints', 'AWS API Gateway', and 'API stages'.

Tighten the 'when' clause to cite concrete trigger situations (e.g. 'Use when creating, deploying, or managing Amazon API Gateway APIs and stages').

Dimension	Reasoning	Score
Specificity	It names the domain ('Amazon API Gateway integration') but the listed actions — 'Manage data, records, and automate workflows' — are generic rather than concrete API Gateway operations like creating APIs or deploying stages, matching 'Names the domain but actions are minimal or generic.'	2 / 5
Completeness	It states a 'what' ('Amazon API Gateway integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Amazon API Gateway data'), but the 'what' is vague and the trigger phrases are not as rich as the level-5 anchor.	4 / 5
Trigger Term Quality	The natural term 'Amazon API Gateway' appears twice and the trigger 'interact with Amazon API Gateway data' is present, but common variations/synonyms (REST API, endpoints, AWS API Gateway, APIs) are missing, matching 'Some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	Naming the specific AWS product gives a clear niche, but the generic 'manage data, records' actions create minor overlap risk with sibling Membrane integration skills, matching 'Mostly distinct; minor overlap risk with closely related skills.'	4 / 5
	Total	13 / 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: membranedev/application-skills
Path: skills/amazon-api-gateway/SKILL.md
Commit: f484c82

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.