CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migrate-to-vinext

Migrates Next.js projects to vinext (Vite-based Next.js reimplementation). Load when asked to migrate, convert, or switch from Next.js to vinext. Handles compatibility scanning, package replacement, Vite config generation, ESM conversion, and deployment setup (Cloudflare Workers natively, other platforms via Nitro).

Quality

94%

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

92%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-engineered migration skill body: copy-paste-ready commands and complete flag tables make it immediately actionable, the phased workflow is gated and validated at the right checkpoints, and detail is cleanly offloaded to three real, purpose-labeled reference files. The only weakness is mild repetition between the Cloudflare sections and the Anti-patterns list.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with virtually no explanations of concepts Claude already knows, but contains minor redundancy: the getPlatformProxy() warning and the native-over-Nitro preference each appear twice (Phase 4 and Anti-patterns), and the bindings section includes trimmable 'why it works' prose. Anchor 4 (efficient with minor over-explanation) fits better than 5, and better than 3 since the padding is isolated rather than systematic.

4 / 5

Actionability

Fully executable throughout: copy-paste commands ('npx vinext init --platform=cloudflare --cdn-cache=response-store ...'), complete flag/value tables, ready vite.config.ts snippets, Cloudflare binding code with 'import { env } from "cloudflare:workers"', and NITRO_PRESET build commands covering the common targets. Matches the 5 anchor with common cases explicitly covered.

5 / 5

Workflow Clarity

A clearly sequenced five-phase workflow with an entry gate ('If not found, STOP — this skill does not apply'), pre-migration validation via 'vinext check', explicit decision branches ('If vinext init succeeds, skip Phase 3'; wrangler-config handling options), and a verification phase that reports errors with full output plus a troubleshooting reference. Meets the 5 anchor's validation-checkpoint and error-recovery bar.

5 / 5

Progressive Disclosure

The body stays an actionable overview and pushes detail to three well-signaled, one-level-deep references (compatibility.md, config-examples.md, troubleshooting.md), all of which exist and only link sideways or back to SKILL.md. Each link states its purpose ('for supported/unsupported features and ecosystem library status'), matching the 5 anchor; not 4 because no detail that belongs in references is inlined and navigation is unambiguous.

5 / 5

Total

19

/

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: it states what the skill does with a comprehensive list of concrete actions, gives an explicit 'Load when...' trigger clause with natural verbs, and defines a clear, conflict-free niche. The only minor gap is synonym coverage of natural trigger phrasings such as 'port' or 'move off Next.js'.

DimensionReasoningScore

Specificity

Names the domain and enumerates five concrete actions — 'compatibility scanning, package replacement, Vite config generation, ESM conversion, and deployment setup' — matching the comprehensive-coverage anchor; it is not score 4 because there are no meaningful gaps in capability coverage.

5 / 5

Completeness

Explicitly answers both questions: 'what' via 'Migrates Next.js projects to vinext... Handles compatibility scanning...' and 'when' via the concrete trigger phrase 'Load when asked to migrate, convert, or switch from Next.js to vinext'. This is a direct match for the 5 anchor, not 4, since the when-clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

'Load when asked to migrate, convert, or switch from Next.js to vinext' supplies three natural user verbs plus product keywords (Next.js, vinext, Vite, Cloudflare). It falls short of the 5 anchor because a few natural phrasings users would say ('port to', 'move off Next.js', 'migrate away from') are absent.

4 / 5

Distinctiveness Conflict Risk

The Next.js-to-vinext migration niche with product-specific triggers is highly distinct and would not fire for unrelated skills; minimal conflict risk, matching the 5 anchor.

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

cloudflare/vinext

Path

.agents/skills/migrate-to-vinext/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.