nextjs-cloudflare-opennext

Assess Next.js repos and plan OpenNext adoption for Cloudflare Workers deployment.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/gmackie/agent-skills --skill nextjs-cloudflare-opennext-gmackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nextjs-cloudflare-opennext
Source: https://github.com/gmackie/agent-skills/tree/main/skills/nextjs-cloudflare-opennext
Command: npx skills add https://github.com/gmackie/agent-skills --skill nextjs-cloudflare-opennext-gmackie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve? Moving a Next.js app onto Cloudflare Workers via OpenNext often fails because of missing adapter setup, unmanaged Wrangler bindings, and local-development drift. This Skill inventories the repo, checks OpenNext prerequisites, and produces a concrete adoption plan before any code changes. ## Core Features & Use Cases - Repo Inventory: Runs a helper script that detects the Next.js router shape, current deployment target, Wrangler configs, OpenNext adapter packages, env files, and binding usage markers. - Binding and Local-Dev Review: Audits Wrangler configuration, typed binding generation, secrets handling, and local versus remote binding strategy. - Adoption Planning: Writes a structured plan to docs/cloudflare/ with fit assessment, required changes, blockers, and rollout sequence. - Use Case: A team wants to deploy their existing Next.js SaaS app on Cloudflare Workers. The Skill confirms the repo is a valid candidate, maps D1/KV/R2 dependencies, and outputs a step-by-step adoption plan for the next implementation agent. ## Quick Start Ask the agent to help move your Next.js app onto Cloudflare Workers with OpenNext and have it produce an adoption plan.

Frequently Asked Questions about nextjs-cloudflare-opennext

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Next.js app to Cloudflare Workers with OpenNext?▼

Start by inventorying the repo with the plan-opennext-adoption.sh helper to detect router shape, deployment target, and existing Cloudflare config. Then verify the @opennextjs/cloudflare adapter and Wrangler setup, map bindings, and follow the generated adoption plan.

How to check if a Next.js repo is ready for OpenNext?▼

Run the helper script against the repo root to detect the next dependency, App or Pages Router shape, Wrangler configs, and binding usage. Compare results against the adoption checklist covering repo fit, platform setup, app surface, and rollout discipline.

Does OpenNext on Cloudflare support D1, KV, and R2 bindings?▼

Yes, Cloudflare bindings like D1, KV, R2, Durable Objects, Queues, and Workflows are supported but must be declared through Wrangler configuration. The Skill audits which bindings are declared, implied in code, or missing local-dev coverage.

OpenNext vs migrating away from Next.js, which should I choose?▼

Choose OpenNext when the app should remain a Next.js app but run on Cloudflare Workers. If the goal is leaving Next.js for a Vite-based path, use the migrate-to-vinext skill instead, as this Skill explicitly does not handle framework rewrites.

Why do first OpenNext deployments to Cloudflare Workers fail?▼

Most failures come from binding and local preview drift rather than missing packages. Common causes include absent Wrangler config, untyped bindings, confusion between .env files and Cloudflare binding access, and unverified secrets in the target environment model.