CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

routing-middleware

Vercel Routing Middleware guidance — request interception before cache, rewrites, redirects, personalization. Works with any framework. Supports Edge, Node.js, and Bun runtimes. Use when intercepting requests at the platform level.

Quality

81%

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 strong, dense reference body: executable examples cover all common routing-middleware cases, decision tables make concept disambiguation unambiguous, and structure is clean throughout. The main costs are a repeated middleware/proxy disambiguation, editorial padding in the rename rationale, and inlined operational detail that would fit better in reference files.

Suggestions

Consolidate the middleware/proxy disambiguation — it currently appears three times (the concept table, the 'Why the rename' paragraph, and the 'Next.js 16' bullet in 'What It Is'); keep the table and trim the prose to one sentence.

Move the project-level routes management details (Dashboard/API/CLI methods, vercel.ts programmatic config) into a one-level-deep reference file and keep a short summary with a clearly signaled link in SKILL.md.

Add a brief verification step for routing changes (e.g., how to confirm which CDN mechanism or runtime handled a request after deploying) to close the workflow's validation gap.

DimensionReasoningScore

Conciseness

The body is dense with Vercel-specific platform facts Claude won't know (runtimes, limits, three CDN mechanisms, Next.js 16 rename) and doesn't pad with generic explanations, matching 'efficient; minor instances of over-explanation'. Not 5 because the rename-rationale paragraph ('\"middleware\" was often confused with Express.js middleware... \\"proxy\\" says what it is') is editorial padding, the disambiguation is repeated across the table, the 'Why the rename' paragraph, and the 'Next.js 16' bullet, and a date-stamped claim ('added March 2026') sits in a main section rather than a deprecated/old-patterns note; not 3 because verbosity is minor, not 'several unnecessary explanations'.

4 / 5

Actionability

Copy-paste-ready code covers the common cases end to end: vercel.json entrypoint config, a complete proxy.ts geo-rewrite example, matcher configurations (single, multiple, regex), IP header injection, A/B via global config, background processing via waitUntil, Bun setup, and the migration codemod command ('npx @next/codemod@latest middleware-to-proxy .'), matching 'fully executable; specific examples cover the common cases'. Not 4 because gaps are trivial (e.g., '8 dedicated endpoints' unnamed), not missing steps for any common case.

5 / 5

Workflow Clarity

For a guidance skill, the decision sequence is clear: three configuration options ranked by preference, a disambiguation table selecting among the three 'middleware' concepts, an ordered evaluation table for the three CDN routing mechanisms, and explicit 'When to Use'/'When NOT to Use' sections — matching 'clear sequence with most checkpoints present'. Not 5 because there are no verification steps (e.g., how to confirm which mechanism handled a request, or that a middleware is actually running); not 3 because sequencing and decision checkpoints are explicit throughout, not implicit.

4 / 5

Progressive Disclosure

With no bundle files, the single-file body is well-organized into scannable sections with two clearly labeled reference links at the end ('docs', 'API reference', 'getting started'), matching 'good structure; most content is appropriately placed; references mostly clear'. Not 5 because some operational detail (project-level routes management methods, programmatic vercel.ts) is inlined where a one-level-deep reference file would keep SKILL.md a leaner overview; not 3 because references are clearly signaled and organization is consistently strong.

4 / 5

Total

17

/

20

Passed

Description

75%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 solid, third-person description that names the domain, lists several concrete capabilities, and includes an explicit 'Use when' clause. Main weaknesses are the narrow single trigger condition and missing natural synonyms (A/B testing, geo, middleware.ts/proxy file names) that would broaden retrieval.

Suggestions

Expand the 'Use when' clause to cover concrete triggers tied to each listed capability, e.g., 'Use when configuring rewrites, redirects, geo-personalization, or A/B routing, or when the user mentions middleware.ts, proxy.ts, or vercel.json routing.'

Add the natural synonyms users say for this domain — 'A/B testing', 'geo-routing', 'middleware.ts', 'proxy.ts' — to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Vercel Routing Middleware') and several concrete actions — 'request interception before cache, rewrites, redirects, personalization' — matching the 'several specific actions; minor gaps' anchor. Not 5 because coverage isn't comprehensive (no mention of A/B testing, header injection, or matcher scoping); not 3 because it lists four distinct actions, not just 1-2.

4 / 5

Completeness

Both parts are present: a clear 'what' ('request interception before cache, rewrites, redirects, personalization') and an explicit 'when' ('Use when intercepting requests at the platform level'). Not 5 because the 'when' clause covers only one narrow trigger and omits concrete phrases tied to the listed capabilities (e.g., 'when the user asks about rewrites or redirects'); not 3 because 'when' is explicitly stated, not merely implied.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'middleware', 'rewrites', 'redirects', 'request interception', 'personalization', plus runtime names users would mention (Edge, Node.js, Bun). Not 5 because common synonyms and trigger phrases users actually say are missing ('A/B testing', 'geo-blocking', 'middleware.ts', 'proxy'); not 3 because coverage goes well beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Clear niche — Vercel platform-level request interception — that is mostly distinct from sibling skills, matching 'minor overlap risk with closely related skills'. Not 5 because the generic term 'middleware' carries real collision risk with framework middleware concepts (Express middleware, Next.js middleware/proxy, auth middleware); not 3 because the Vercel/platform scoping keeps it well above 'could still overlap with similar skills'.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

vercel/vercel-plugin

Path

skills/routing-middleware/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.