building-api-gateway
Create API gateways with routing, load balancing, rate limiting, and authentication. Use when routing and managing multiple API services. Trigger with phrases like "build API gateway", "create API router", or "setup API gateway".
72
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/api-development/api-gateway-builder/skills/building-api-gateway/SKILL.mdQuality
Discovery
92%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 is a well-structured description that clearly communicates specific capabilities and includes explicit trigger guidance. It covers the what/when effectively and uses natural language terms. The main weakness is potential overlap with skills focused on individual concerns like authentication or rate limiting in non-gateway contexts.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: routing, load balancing, rate limiting, and authentication. These are distinct, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (create API gateways with routing, load balancing, rate limiting, authentication) and 'when' (explicit 'Use when' clause and 'Trigger with phrases' providing concrete activation scenarios). | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases like 'build API gateway', 'create API router', 'setup API gateway', plus keywords like 'routing', 'load balancing', 'rate limiting', and 'authentication' that users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | While 'API gateway' is fairly specific, individual capabilities like 'rate limiting' or 'authentication' could overlap with other skills focused on those specific concerns. The description could conflict with general API development or authentication-focused skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-organized with good progressive disclosure and clear output expectations, but critically lacks actionable, executable content. The instructions read as a high-level architecture description rather than concrete implementation guidance—no code snippets, no configuration examples, no commands. The workflow sequencing is present but missing validation checkpoints needed for this complexity level.
Suggestions
Add executable code snippets for key steps—e.g., a concrete route configuration YAML, a JWT validation middleware implementation, and a circuit breaker setup with actual library calls.
Include validation checkpoints in the workflow—e.g., 'Test routing with curl after step 2', 'Verify auth rejection with invalid token after step 3', 'Confirm circuit breaker triggers after step 7'.
Replace the abstract example descriptions with concrete input/output examples showing actual request/response pairs or configuration snippets.
Remove the verbose overview paragraph that restates what the instructions already cover to improve token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably structured but includes unnecessary verbosity in places—the overview restates what the instructions cover, the prerequisites explain obvious concepts, and the examples section describes scenarios without providing executable code. Some tightening would help. | 2 / 3 |
Actionability | Despite listing 9 steps, the instructions are entirely descriptive and abstract—there is no executable code, no concrete configuration snippets, no copy-paste-ready commands. Steps like 'Implement authentication at the gateway layer' and 'Add rate limiting' are vague directions, not actionable guidance. The real implementation is deferred to a reference file. | 1 / 3 |
Workflow Clarity | Steps are sequenced logically and numbered, but there are no validation checkpoints, no feedback loops for error recovery, and no explicit verification between steps. For a complex multi-step process involving routing, auth, and circuit breakers, the absence of validation steps is a significant gap. | 2 / 3 |
Progressive Disclosure | The skill appropriately structures content with a clear overview, well-organized sections, and one-level-deep references to implementation.md, errors.md, and examples.md. Output files are clearly listed and navigation is straightforward. | 3 / 3 |
Total | 8 / 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
70e9fa4
- 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.