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.
41
11%
Does it follow best practices?
Impact
99%
1.05xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/13-aws-skills/api-gateway-config/SKILL.mdQuality
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 severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks any concrete actions, capabilities, or explicit usage guidance. The only useful element is the mention of 'api gateway config' as a trigger term, but even this is duplicated and lacks natural variations.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures AWS API Gateway REST APIs, sets up routes, manages stages, configures authentication and throttling.'
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user needs to create API endpoints, configure API Gateway stages, set up API authentication, or manage AWS REST/HTTP APIs.'
Include natural keyword variations users might say: 'API Gateway', 'REST API setup', 'API endpoints', 'API stages', 'Lambda integration', '.yaml API config'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Api Gateway Config' is just a name, not a description of capabilities. There are no verbs describing what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' entirely - there are no capabilities listed. The 'when' is only implied through trigger terms but lacks explicit guidance like 'Use when...' clause. | 1 / 3 |
Trigger Term Quality | Contains 'api gateway config' as a trigger term which is somewhat relevant, but it's duplicated and lacks natural variations users might say like 'API Gateway setup', 'configure API endpoints', 'REST API', 'AWS API Gateway', or 'gateway routes'. | 2 / 3 |
Distinctiveness Conflict Risk | While 'API Gateway' is somewhat specific to AWS, the description is so vague it could overlap with other AWS skills or general API configuration skills. The lack of specific actions makes it hard to distinguish from related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%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 with no actual API Gateway configuration content. It consists entirely of generic boilerplate that could apply to any skill, providing zero actionable guidance for configuring AWS API Gateway. The skill fails all dimensions as it contains no concrete code, commands, examples, or workflows.
Suggestions
Add concrete API Gateway configuration examples using AWS CLI commands or CloudFormation/Terraform templates (e.g., creating REST APIs, configuring routes, setting up authorizers)
Include executable code snippets for common tasks like creating API endpoints, configuring CORS, setting up Lambda integrations, and defining request/response mappings
Define a clear workflow for API Gateway setup with validation steps (e.g., deploy -> test endpoint -> verify responses -> check CloudWatch logs)
Add references to related documentation for advanced topics like custom domains, usage plans, API keys, and WebSocket APIs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual API Gateway configuration guidance. It explains what the skill does in abstract terms rather than providing any concrete information Claude doesn't already know. | 1 / 3 |
Actionability | No concrete code, commands, or specific examples are provided. The content only describes what the skill claims to do without any executable guidance for API Gateway configuration. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. The skill mentions 'step-by-step guidance' but provides none. There are no validation checkpoints or sequences for API Gateway configuration tasks. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to detailed materials, examples, or related documentation. No structure for discovery or navigation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%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 | |
- Commit
0c08951
- Reviewed
Table of Contents
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.