CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nextjs-on-cloudflare

Build, migrate, and deploy Next.js apps on Cloudflare Workers with vinext. Use when starting a Next.js project on Cloudflare, moving an existing app to Workers, choosing between vinext and OpenNext, or setting up vinext for Workers. For setup, migration, or deployment, install vinext's upstream skills with `npx skills add cloudflare/vinext` if missing, then read and follow the applicable skill and docs.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-structured routing skill: concise, scenario-specific guidance with a copy-paste install command, guardrails against misapplying the migration skill, and a clean fallback path. The small gaps are a trimmable "Why vinext" feature list and reliance on external upstream skills for execution details.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, and the "Why vinext" section is justified because the tool is novel, but the four-bullet feature list ("Familiar Next.js development: App Router, Pages Router..."; "Vite tooling: fast HMR, native ESM") is mildly promotional and could be condensed to one line since the Cloudflare-guide default already carries the recommendation. This matches the 4 anchor (minor over-explanation that could be trimmed) rather than 5.

4 / 5

Actionability

Concrete guidance throughout: the copy-paste command "npx skills add cloudflare/vinext", per-scenario routing to named upstream skills and docs (e.g., "follow vinext's new-project setup using create-vinext-app with the Cloudflare target"), and an explicit fallback ("If installation is unavailable, read the linked upstream SKILL.md and relevant references directly"). It falls short of the 5 anchor because executable details (deploy commands, configuration) are delegated to external upstream skills rather than present in this file.

4 / 5

Workflow Clarity

The sequence is clear and well-guarded: check for upstream skills, install if missing, route by scenario (new project / existing project / development and deployment), with an explicit checkpoint ("The upstream migration skill requires an existing Next.js project; do not apply it to an empty directory") and an error-recovery fallback for install failure. No destructive or batch operations are involved, and the simple-skill exception applies — the single routing action is unambiguous.

5 / 5

Progressive Disclosure

At under 50 lines with well-organized sections, the body keeps only overview content inline, clearly signals its single one-level-deep reference ("read [references/skill-feedback.md](references/skill-feedback.md)", verified to exist), and points scenario details to clearly labeled external upstream docs. This matches the 5 anchor for short, well-structured skills.

5 / 5

Total

18

/

20

Passed

Description

96%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 actions, an explicit "Use when" clause with natural trigger phrases, and a clear niche. The only weakness is minor trigger overlap with a hypothetical OpenNext skill for generic Next.js-on-Cloudflare deployment requests.

DimensionReasoningScore

Specificity

"Build, migrate, and deploy Next.js apps on Cloudflare Workers with vinext" lists multiple concrete actions (build, migrate, deploy, choose, set up) plus an executable install command ("npx skills add cloudflare/vinext"), giving comprehensive coverage of the skill's domain. This matches the 5 anchor rather than 4 because no capability area of the skill is left unlisted.

5 / 5

Completeness

It explicitly answers "what" ("Build, migrate, and deploy Next.js apps on Cloudflare Workers with vinext") and "when" ("Use when starting a Next.js project on Cloudflare, moving an existing app to Workers, choosing between vinext and OpenNext, or setting up vinext for Workers") with concrete trigger phrases, exactly mirroring the 5 anchor's structure.

5 / 5

Trigger Term Quality

Natural user phrasings are comprehensively covered: "starting a Next.js project on Cloudflare", "moving an existing app to Workers", "choosing between vinext and OpenNext", plus tool names (vinext, OpenNext, Workers). No natural term a user would say for this need is missing, matching the 5 anchor.

5 / 5

Distinctiveness Conflict Risk

The niche (Next.js on Cloudflare Workers with vinext) is clear and specific, but a trigger like "deploy my Next.js app to Cloudflare" without naming a tool would equally match a closely related OpenNext skill, and the description explicitly claims the "choosing between vinext and OpenNext" decision. That minor overlap with a closely related skill fits the 4 anchor better than the 5 anchor's "minimal conflict risk".

4 / 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

cloudflare/skills

Path

skills/nextjs-on-cloudflare/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.