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.
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill api-gateway-configActivation
22%This description is severely underdeveloped, providing almost no actionable information about what the skill does or when to use it. It relies entirely on category membership ('AWS Skills') and a single repeated trigger phrase without describing any concrete capabilities. The description fails to help Claude distinguish this skill from other AWS or configuration-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates, configures, and deploys AWS API Gateway REST and HTTP APIs, manages routes, integrations, stages, and authorization settings.'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user needs to set up API Gateway, configure REST APIs, manage API routes, deploy API stages, or work with Lambda integrations.'
Expand trigger terms to include variations users naturally say: 'API Gateway', 'REST API', 'HTTP API', 'API endpoints', 'gateway deployment', 'API stages', 'Lambda proxy'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - it only states it's an 'auto-activating skill' without describing what it actually does with API Gateway configurations (create, modify, deploy, troubleshoot, etc.). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond vague categorization, and has no explicit 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains 'api gateway config' as a trigger term (duplicated), which is somewhat relevant but misses natural variations users might say like 'API Gateway', 'REST API', 'HTTP API', 'gateway setup', 'API endpoints', or AWS-specific terms. | 2 / 3 |
Distinctiveness Conflict Risk | Being part of 'AWS Skills' category provides some distinction, but 'api gateway config' is vague enough to potentially conflict with other AWS-related skills or general configuration skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill is an empty template that provides zero actionable content about API Gateway configuration. It consists entirely of meta-description about what the skill claims to do without any actual instructions, code examples, configuration patterns, or AWS-specific guidance. The content would be identical if you replaced 'api gateway config' with any other topic.
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 specific code examples for common patterns like Lambda integration, request/response mapping templates, and CORS configuration
Define a clear workflow for API Gateway setup with validation steps (e.g., 1. Create API -> 2. Configure routes -> 3. Deploy to stage -> 4. Test endpoint)
Add references to related skills or documentation for advanced topics like custom domains, usage plans, and API keys
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual API Gateway configuration information. It explains what the skill does in generic terms without providing any concrete guidance, wasting tokens on meta-description rather than actionable content. | 1 / 3 |
Actionability | No concrete code, commands, or specific examples are provided. The content describes rather than instructs - phrases like 'Provides step-by-step guidance' and 'Generates production-ready code' promise capabilities without delivering any actual guidance or code. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, sequences, or validation checkpoints for API Gateway configuration tasks. The skill merely states it will provide guidance without actually providing any. | 1 / 3 |
Progressive Disclosure | No structure for progressive disclosure exists. There are no references to detailed documentation, no links to related files, and no organization of content by complexity or use case. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.