api-gateway-config

Api Gateway Config - Auto-activating skill for AWS Skills. Triggers on: api gateway config, api gateway config Part of the AWS Skills skill category.

1.05x

Quality

11%

Does it follow best practices?

Impact

99%

1.05x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/api-gateway-config/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is extremely minimal and fails to communicate what the skill actually does beyond naming the AWS service it relates to. It lacks concrete actions, meaningful trigger term variety, and any explicit 'when to use' guidance. The duplicate trigger term ('api gateway config' listed twice) suggests a template was filled in without care.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates and configures AWS API Gateway REST and HTTP APIs, sets up routes, manages stages, configures throttling and authorization.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to set up API Gateway, configure API routes, manage API stages, or work with REST/HTTP APIs in AWS.'

Expand trigger terms to include natural variations users would say: 'API Gateway', 'REST API', 'HTTP API', 'API endpoints', 'API routes', 'gateway configuration', '.tf API Gateway'.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. It only states it is an 'auto-activating skill for AWS Skills' without describing what it actually does with API Gateway configurations (e.g., create routes, configure endpoints, set up throttling, manage stages).	1 / 3
Completeness	The 'what' is essentially missing—there is no description of what the skill actually does beyond its name. While there is a 'Triggers on' clause, the lack of any meaningful 'what' makes this incomplete. The 'when' is only implied through the trigger terms.	1 / 3
Trigger Term Quality	It includes 'api gateway config' as a trigger term, which is somewhat relevant, but it duplicates the same trigger and misses common variations users would say like 'API Gateway', 'REST API', 'HTTP API', 'API routes', 'API endpoints', 'gateway setup', or 'AWS API Gateway'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'API Gateway' provides some specificity within the AWS domain, but 'config' is vague and could overlap with other AWS configuration skills. Without specifying what kind of API Gateway operations it handles, it could conflict with general AWS infrastructure or networking skills.	2 / 3
	Total	6 / 12 Passed

Implementation

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

This skill is an empty template/placeholder with no actual content about API Gateway configuration. It contains no executable code, no specific AWS guidance, no workflows, and no references to supporting materials. It would provide zero value to Claude when attempting to help a user configure an API Gateway.

Suggestions

Add concrete, executable examples such as AWS CLI commands for creating REST/HTTP APIs, SAM/CloudFormation templates for API Gateway resources, and CDK snippets for common configurations.

Define a clear workflow for API Gateway setup: e.g., 1) Create API, 2) Define routes/methods, 3) Configure integrations (Lambda, HTTP), 4) Set up stages, 5) Deploy and validate with a curl test.

Include specific configuration patterns like CORS setup, custom domain configuration, authorizer setup (Cognito/Lambda), throttling/rate limiting, and request/response mapping templates.

Remove all generic boilerplate sections (Purpose, When to Use, Example Triggers) and replace with actionable content that teaches Claude something it doesn't already know about API Gateway configuration.

Dimension	Reasoning	Score
Conciseness	The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'api gateway config' excessively, and provides zero domain-specific information. Every section is padded with generic template language.	1 / 3
Actionability	There are no concrete code examples, no specific AWS CLI commands, no CloudFormation/SAM/CDK snippets, no API Gateway configuration details whatsoever. The content describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any.	1 / 3
Workflow Clarity	There is no workflow, no sequence of steps, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for configuring an API Gateway.	1 / 3
Progressive Disclosure	There are no references to supporting files, no links to detailed guides, and no bundle files exist. The content is a shallow placeholder with no meaningful structure or navigation to deeper material.	1 / 3
	Total	4 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3a2d27d

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.