vercel-to-cloudflare-migrator
Vercel → Cloudflare Migrator
Analyze a Next.js-on-Vercel repository, pull real billing data from Vercel, estimate the projected monthly bill on Cloudflare Workers, provision the replacement Cloudflare resources, and open a draft PR that wires them in. App-code rewrites of @vercel/* data clients are reported, not applied — this skill's code changes stop at the deployment scaffolding layer.
Severity levels used throughout: BLOCKER (migration can't proceed as-is) · HIGH (needs rewrite before cutover) · MEDIUM (works but degraded) · LOW (cosmetic / best practice) · PASS (no issue).
Phase 1: Project Detection
Use Glob, Grep, and Read only — no network calls in this phase.
Required signals
Both must be present, otherwise stop and tell the user this skill targets Next.js apps currently on Vercel.
| Signal | Category |
|---|---|
next in dependencies of any package.json |
nextjs |
vercel.json OR .vercel/ OR .vercelignore present |
vercel |
More from erezrokah/skills
supply-chain-auditor
Audit a repository for supply chain security risks. Use when the user asks to audit supply chain security, check dependency pinning, review GitHub Actions security, or harden CI/CD. Activate for partial matches like "are my deps pinned?" or "is my CI safe?".
13you-dont-need-isr
Audit a Next.js project's Incremental Static Regeneration usage and suggest simpler alternatives where ISR is overkill. Use when the user asks to evaluate ISR, check if ISR is necessary, simplify a Next.js caching strategy, or wants to know "do I actually need ISR?". Activate for partial matches like "should I be using ISR?", "ISR or SSG?", "is revalidate worth it?", or "my Next.js caching is confusing".
4