CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webiny-http-route

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

Quality

90%

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

82%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 highly actionable, well-organized reference: executable examples throughout, gotchas called out prominently, and clear structure. Weaknesses are minor — slight duplication, no explicit verification step, and everything inlined in one file.

Suggestions

De-duplicate the 'handler reads its own identity via request.route' explanation (Request section vs. decorator section) and the repeated createImplementation boilerplate to tighten conciseness.

Add a short verification step (e.g., curl the deployed route or check deploy output) after the deploy command to close the workflow-clarity gap.

Consider moving the two decorator examples into a references/ file linked from a brief 'Decorating a route' section, keeping SKILL.md as a leaner overview.

DimensionReasoningScore

Conciseness

Dense, gotcha-driven content with no padding or explanation of known concepts, but minor duplication: the handler-reads-its-own-identity point appears in both the Request section and the decorator section, and the createImplementation boilerplate repeats across examples.

4 / 5

Actionability

Copy-paste-ready handler code, registration JSX, a complete props table, response method table, two full decorator examples, and a deploy command — the common cases are fully covered with executable guidance.

5 / 5

Workflow Clarity

The TL;DR and Quick reference give a clear write-handler → register → deploy sequence, and build-failure feedback ('Omitting it fails the build', 'build stops when two routes share a name') is documented, but there is no explicit post-deploy verification checkpoint.

4 / 5

Progressive Disclosure

No bundle files exist; the single ~250-line file is cleanly sectioned and easy to navigate. The decorator examples and response API could arguably live in reference files, but inline placement is defensible at this scope.

4 / 5

Total

17

/

20

Passed

Description

92%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 description: concrete, framework-specific actions with an explicit multi-clause 'Use when' trigger. The only gap is missing common synonyms (e.g., REST endpoint) in the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with named artifacts — 'expose a custom HTTP endpoint (GET, POST, PUT, etc.)', 'implement a route handler with full DI support', 'register a custom HTTP route in webiny.config.tsx' — comprehensively covering the skill's scope; no generic filler.

5 / 5

Completeness

Explicitly answers both: 'what' in the first sentence (adding custom HTTP routes with <Api.Route> and HttpRouteHandler) and 'when' via three concrete trigger clauses in 'Use this skill when the developer wants to...'.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('custom HTTP endpoint', 'route handler', 'GET, POST, PUT', 'custom HTTP route'), but common synonyms such as 'REST endpoint' or 'webhook' are missing. Above a 3 because it includes method names and the config-file trigger, below a 5 because synonym coverage is incomplete.

4 / 5

Distinctiveness Conflict Risk

Webiny-specific triggers (webiny.config.tsx, Api.Route, HttpRouteHandler) and the 'alongside the GraphQL handler' framing carve a clear HTTP-route niche with minimal overlap risk against a GraphQL-endpoint skill.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

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.