CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is well-structured with strong progressive disclosure and good conciseness, but the body relies on prose rather than inline executable examples and lacks explicit validation checkpoints within its workflow, capping actionability and workflow clarity.

Suggestions

Add a short inline runnable snippet (e.g., a minimal routes.yaml or Express proxy stub) in the Instructions or Output section so guidance is copy-paste ready rather than only in references.

Insert an explicit validation checkpoint earlier in the workflow (e.g., 'After defining routes, load routes.yaml and verify each upstream health before enabling auth/rate limiting') with a fix-and-retry loop, not just a final test step.

Tighten the long Overview sentence into a shorter summary, moving architectural detail into the implementation reference to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the single Overview sentence is dense and a few instruction steps could be tightened, so it sits between the efficient (3) and mostly-efficient (2) anchors.

2.5 / 3

Actionability

Steps name concrete outputs, headers, and status codes, but the body itself offers prose guidance rather than inline executable code — the copy-paste examples live in the bundled references — matching the 'some concrete guidance but incomplete' anchor and falling short of copy-paste-ready (3).

2 / 3

Workflow Clarity

The 9-step sequence is clear, but the only validation is a final integration-test step (step 9) with no explicit validate-then-proceed checkpoint or error-recovery feedback loop, which caps workflow clarity at 2 per the destructive/batch-operations guideline.

2 / 3

Progressive Disclosure

A concise overview body points to three clearly signaled, one-level-deep reference files (implementation.md, errors.md, examples.md) that all exist and hold appropriately split content, matching the well-structured anchor.

3 / 3

Total

9.5

/

12

Passed

Description

100%

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

The description is concise, specific, and complete: it names concrete capabilities, gives an explicit 'Use when' trigger clause, lists natural trigger phrases, and occupies a clear niche unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'routing, load balancing, rate limiting, and authentication' — in third person, matching the multi-action anchor rather than the single-action (2) or vague (1) anchors.

3 / 3

Completeness

Explicitly answers both what ('Create API gateways with routing, load balancing, rate limiting, and authentication') and when ('Use when routing and managing multiple API services'), matching the score-3 anchor with an explicit 'Use when' clause.

3 / 3

Trigger Term Quality

Provides natural trigger phrases ('build API gateway', 'create API router', 'setup API gateway') a user would plausibly say, giving good coverage rather than just one keyword.

3 / 3

Distinctiveness Conflict Risk

'API gateway' is a clear niche with distinct, specific triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.