CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-http-route

Adding custom HTTP routes to the API using Api.Route and Route.Interface. Use this skill when the developer wants to expose a custom HTTP endpoint (GET, POST, PUT, etc.) on the API Gateway alongside the GraphQL handler, implement Route.Interface with full DI support, or register a custom HTTP handler in webiny.config.tsx.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is lean, actionable, and well-structured: two complete executable examples, a props table, interface definitions, explicit build-failure guardrails, and a quick-reference block, all without explaining concepts Claude already knows. The only minor gap is the absence of an explicit validate->fix->retry loop for the deploy step, but the single-action nature and explicit guardrails keep workflow clarity strong.

DimensionReasoningScore

Conciseness

The body is dense with actionable technical content and assumes Claude's competence throughout, with no padding explaining HTTP, DI, or Fastify; every section (TL;DR, props table, interfaces, key rules, quick reference) earns its place, matching the score-3 'lean and efficient' anchor rather than the score-2 'could be tightened'.

3 / 3

Actionability

Provides fully executable TypeScript examples with real imports, a complete props reference table, concrete interface definitions, exact registration JSX, and a copy-paste-ready Quick Reference, matching the score-3 'fully executable code; copy-paste ready' anchor rather than the score-2 'pseudocode instead of executable code'.

3 / 3

Workflow Clarity

The single-pattern workflow (write handler -> export default -> register in config -> deploy) is unambiguous and reinforced by explicit 'YOU MUST' guardrails acting as checkpoints ('Omitting the file extension will cause a build failure'); per the simple-skill scoring note an unambiguous single action can score 3, though a concrete validate/retry command for the deploy step is the one thing that could push it beyond an implicit checkpoint.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the body is a single self-contained file well-organized into clearly labeled sections, which per the under-50-line / no-external-references guideline scores 3, matching the 'clear overview with well-organized sections' anchor rather than the score-2 'content that should be separate is inline'.

3 / 3

Total

12

/

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, concrete, and uses third-person voice while clearly stating both capabilities and explicit use-when triggers. It lists several specific actions with named framework primitives and is well-distinguished from related skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with named framework primitives ('Adding custom HTTP routes to the API using Api.Route and Route.Interface', 'implement Route.Interface with full DI support', 'register a custom HTTP handler in webiny.config.tsx'), matching the 'lists multiple specific concrete actions' anchor rather than the score-2 'names domain and some actions'.

3 / 3

Completeness

Explicitly answers both 'what' ('Adding custom HTTP routes to the API using Api.Route and Route.Interface') and 'when' via a clear 'Use this skill when the developer wants to...' trigger clause, matching the score-3 anchor instead of the score-2 case where 'when' is only implied.

3 / 3

Trigger Term Quality

Includes natural developer-facing terms ('custom HTTP endpoint', 'GET, POST, PUT', 'API Gateway', 'custom HTTP handler') that a user would naturally say, with good coverage of method variations, fitting the score-3 anchor rather than the score-2 'some relevant keywords but missing common variations'.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (custom HTTP routes on the API Gateway alongside the GraphQL handler) with specific primitives (Api.Route, Route.Interface, webiny.config.tsx), making it distinct from sibling GraphQL skills and unlikely to trigger for the wrong skill, matching the score-3 anchor.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
webiny/webiny-js
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.