building-api-gateway
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill building-api-gatewayCreate 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".
61%
Overall
Validation
Implementation
Activation
Validation
81%| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md line count is 72 (<= 500) | Pass |
frontmatter_valid | YAML frontmatter is valid | Pass |
name_field | 'name' field is valid: 'building-api-gateway' | Pass |
description_field | 'description' field is valid (230 chars) | Pass |
description_voice | 'description' uses third person voice | Pass |
description_trigger_hint | Description includes an explicit trigger hint | Pass |
compatibility_field | 'compatibility' field not present (optional) | Pass |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
metadata_field | 'metadata' field not present (optional) | Pass |
license_field | 'license' field is present: MIT | Pass |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_present | SKILL.md body is present | Pass |
body_examples | Examples detected (code fence or 'Example' wording) | Pass |
body_output_format | Output/return/format terms detected | Pass |
body_steps | Step-by-step structure detected (ordered list) | Pass |
Total | 13 / 16 Passed |
Implementation
22%This skill content is a thin template that lacks concrete, actionable guidance. It describes what an API gateway builder should do at a high level but provides no executable code, specific commands, or real examples. The workflow has structural issues (duplicate numbering) and missing validation steps for what should be a complex multi-step process.
Suggestions
- Add concrete, executable code examples for at least one framework (e.g., Express.js gateway setup with actual routing code)
- Fix the duplicate step numbering and add explicit validation checkpoints (e.g., 'Test endpoint responds before adding middleware')
- Replace the vague 'Bash(api:gateway-*)' reference with actual commands or explain what tools/scripts are available
- Remove the duplicate 'This skill provides automated assistance' sentences and generic prerequisites that Claude already understands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary boilerplate like 'This skill provides automated assistance for api gateway builder tasks' repeated twice, and generic prerequisites that Claude would know. However, the output structure and references are reasonably efficient. | 2 / 3 |
Actionability | Provides only vague, abstract guidance with no concrete code examples, commands, or executable snippets. Instructions like 'Generate boilerplate code using Bash(api:gateway-*)' lack specifics on what that command actually does or looks like. | 1 / 3 |
Workflow Clarity | Steps are poorly organized with duplicate numbering (two separate lists both starting at 1), no validation checkpoints, and no feedback loops for error recovery. The workflow jumps from planning to implementation without clear sequencing. | 1 / 3 |
Progressive Disclosure | References external files for implementation details, errors, and examples which is good structure, but the main content is thin and the references feel like placeholders rather than well-signaled navigation to substantive content. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, natural trigger terms, explicit usage guidance, and clear differentiation from other skills. The description follows best practices by using third person voice and including a dedicated trigger phrase section.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'routing, load balancing, rate limiting, and authentication' - these are distinct, actionable capabilities for API gateway creation. | 3 / 3 |
Completeness | Clearly answers both what (create API gateways with specific features) and when (routing/managing multiple API services) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'build API gateway', 'create API router', 'setup API gateway', plus domain terms like 'routing', 'API services', 'rate limiting'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on API gateways with distinct triggers; unlikely to conflict with general API skills or other infrastructure skills due to specific gateway terminology. | 3 / 3 |
Total | 12 / 12 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.