Name: webiny-http-route
Rating: 72.8 (1 reviews)
Author: webiny

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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

90%Weight 40%Scale 1-5

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

A tight, highly actionable skill body with executable code, a props reference, and a clear build/deploy model — it assumes Claude's intelligence and avoids padding. The only gaps are a missing post-deploy validation checkpoint and the absence of any split-out reference files.

Suggestions

Add an explicit verification step after deploy (e.g., curl the registered route or check Pulumi output) to give the workflow a validation checkpoint.

Consider moving the Route.Request/Route.Reply interface reference and the full HTTP-method list into a separate references file, keeping SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what HTTP routes, Fastify, or DI are, and every section (TL;DR, props table, interfaces, quick reference) earns its place.	5 / 5
Actionability	Provides fully executable, copy-paste-ready TypeScript and TSX examples plus a props table, interface definitions, and a Quick Reference covering the common GET/POST path-parameter cases.	5 / 5
Workflow Clarity	The build-time vs deploy-time (Pulumi) sequence is clearly laid out with a concrete deploy command, but there is no explicit validation/verification checkpoint after registration or deploy, leaving it just below the level-5 anchor.	4 / 5
Progressive Disclosure	Content is well organized into clearly labeled sections with no deep nesting and no orphaned references (no bundle files exist), but everything is inlined in one ~165-line file rather than split into one-level-deep reference files, so it sits at good-but-not-exemplary structure.	4 / 5
	Total	18 / 20 Passed

Description

87%Weight 40%Scale 1-5

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

A strong, third-person description that clearly states the capability and gives explicit 'Use when...' trigger guidance covering endpoint exposure, Route.Interface implementation, and handler registration. Minor keyword/synonym gaps keep specificity and trigger quality just below maximum.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'implement Route.Interface with full DI support' and 'register a custom HTTP handler in webiny.config.tsx' — with only minor coverage gaps, fitting the 'several specific actions' anchor rather than the fully comprehensive level 5.	4 / 5
Completeness	Explicitly answers 'what' ('Adding custom HTTP routes to the API using Api.Route and Route.Interface') and 'when' ('Use this skill when the developer wants to expose a custom HTTP endpoint... implement Route.Interface... or register a custom HTTP handler'), matching the anchor that requires concrete trigger phrases for both.	5 / 5
Trigger Term Quality	Natural terms like 'custom HTTP endpoint (GET, POST, PUT, etc.)', 'API Gateway', 'GraphQL handler', and 'webiny.config.tsx' give good keyword coverage; not quite level 5 because a few common synonyms and the ANY-method mention are absent.	4 / 5
Distinctiveness Conflict Risk	The webiny HTTP-route niche is clearly distinct from the GraphQL alternative and related DI/infrastructure skills, with minimal conflict risk from its specific triggers.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: webiny/webiny-js
Path: skills/user-skills/api/http-route/SKILL.md
Commit: 3e28ba6

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.