Skip to main content
hc
Submit
skillsFirst-partyReview first Safety ✓ Privacy ✓
Cloudflare logo

OpenNext Cloudflare Capability Pack Skill

Expert OpenNext + Cloudflare capability skill for Next.js on Workers, runtime constraints, cache strategy, and production-safe deploy architecture.

by JSONbored·added 2026-04-10·
Claude CodeCodexWindsurfGeminiCursorCLI
HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:expertType:capability-packVerified:validated
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/skills/opennext-cloudflare-capability-pack
Source URLs
https://opennext.js.org/cloudflare/get-started, https://github.com/JSONbored/awesome-claude/blob/main/content/skills/opennext-cloudflare-capability-pack.mdx
Brand
Cloudflare
Brand domain
cloudflare.com
Brand asset source
brandfetch
Package URL
/downloads/skills/opennext-cloudflare-capability-pack.zip
Package SHA256
0254c5d9edfe925907cfca3f06a24c866ecd42e1e7ef51ad64b2a5518199360c
Safety notes
May produce commands or configuration for live infrastructure, CI, releases, or indexing; test changes in staging or dry-run mode first., Use least-privilege API tokens and review workflow, deploy, DNS, cache, and release changes before applying them to production.
Privacy notes
Inputs can include repository metadata, workflow logs, deployment settings, domain names, analytics exports, and service configuration., Redact tokens, account IDs, private URLs, customer data, and proprietary deployment details before sharing generated reports or prompts.
Platform compatibility
claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
Author
JSONbored
Claim status
unclaimed
Last verified
2026-04-10

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as first-party.

    Done

  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    Package marked verified.

    Done

  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

Install command

Provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

3 to clear

Platforms

6 listed

Difficulty

88/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    Listing has review metadata.

    Done

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup. Have accounts and credentials ready first.

0/3 ready
Account & credentials1Install & runtime1Configuration1

Safety & privacy surface

Safety & privacy surface

2 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens.

3 areas
  • SafetyExecution & processesMay produce commands or configuration for live infrastructure, CI, releases, or indexing; test changes in staging or dry-run mode first.
  • SafetyCredentials & tokensUse least-privilege API tokens and review workflow, deploy, DNS, cache, and release changes before applying them to production.
  • PrivacyData retentionInputs can include repository metadata, workflow logs, deployment settings, domain names, analytics exports, and service configuration.
  • PrivacyCredentials & tokensRedact tokens, account IDs, private URLs, customer data, and proprietary deployment details before sharing generated reports or prompts.

Safety notes

  • May produce commands or configuration for live infrastructure, CI, releases, or indexing; test changes in staging or dry-run mode first.
  • Use least-privilege API tokens and review workflow, deploy, DNS, cache, and release changes before applying them to production.

Privacy notes

  • Inputs can include repository metadata, workflow logs, deployment settings, domain names, analytics exports, and service configuration.
  • Redact tokens, account IDs, private URLs, customer data, and proprietary deployment details before sharing generated reports or prompts.

Prerequisites

  • Next.js codebase and Cloudflare account
  • Wrangler configuration access
  • Deployment environment separation (dev/prod)

Schema details

Install type
package
Reading time
10 min
Difficulty score
88
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
0254c5d9edfe925907cfca3f06a24c866ecd42e1e7ef51ad64b2a5518199360c
Skill and platform metadata
Skill type
capability-pack
Skill level
expert
Verification
validated
Verified at
2026-04-10
Retrieval sources
https://opennext.js.org/cloudflare/get-startedhttps://developers.cloudflare.com/workers/framework-guides/web-apps/nextjs/https://developers.cloudflare.com/workers/
Tested platforms
ClaudeCodexOpenClawCursorWindsurfGemini
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Use the OpenNext Cloudflare capability pack for this deployment plan."

# Required output
1) Runtime architecture map
2) Binding/env/secret model
3) Cache and revalidation strategy
4) Deploy and rollback procedure

About this resource

Knowledge Freshness

This capability pack is pinned to documentation verified on 2026-04-10. When upstream docs change, refresh endpoint contracts, examples, and constraints before using this skill for production changes.

Retrieval Sources

Always prefer direct retrieval from official docs/API references over model memory for limits, endpoint signatures, and behavior guarantees.

Core Workflow

  1. Confirm target version/runtime and pull latest official docs for the task scope.
  2. Build an execution plan with explicit read-only discovery before any mutation.
  3. Validate contracts, permissions, and safety constraints before applying changes.
  4. Execute with deterministic checkpoints and rollback criteria.
  5. Produce a verification report with evidence, caveats, and next actions.

Overview

This capability pack teaches agents how to correctly design, deploy, and operate Next.js workloads on Cloudflare Workers using OpenNext. It is tuned for production behavior, not toy deployments.

Capability Scope

  • OpenNext build/runtime model on Workers
  • Binding strategy (D1, KV, R2, secrets, env vars)
  • Cache behavior and invalidation patterns
  • Route-specific security and performance controls
  • Observability, alerting, and rollout safety

Compatibility

Native

  • Claude Code / Claude: native skill usage via SKILL.md.
  • Codex/OpenAI workflows: compatible with Agent Skills-style SKILL.md content as reusable workflow instructions.

Manual Adaptation

  • Gemini CLI: native skill usage via .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported.
  • Cursor: use the generated .cursor/rules/*.mdc adapter for project rules.
  • OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.

Production Rules

  • Treat API routes and static routes with separate cache/security policies.
  • Keep secret values out of repo and build output.
  • Verify behavior in dev and prod workers separately.
  • Enforce explicit rollback and incident pathways.

Troubleshooting

Issue: Unexpected cache behavior after deploy
Fix: Validate cache headers, Cloudflare cache rules, and OpenNext route semantics together.

Issue: Local works, Worker fails
Fix: Check bindings/env parity and runtime-specific API differences.

Issue: Deploys are correct but latency is inconsistent
Fix: Profile critical routes, tighten cache strategy, and isolate expensive dynamic operations.

Output Contract

  1. Provide an implementation plan ordered by risk and dependency.
  2. Provide exact production-ready config/commands with no placeholders.
  3. Call out secrets, permissions, and least-privilege requirements.
  4. Include rollback and recovery guidance for each risky step.

Validation Checklist

  • Verify all referenced docs/versions before applying changes.
  • Run regression checks for core user flow and error paths.
  • Confirm observability/logging is enabled for changed components.
  • Confirm security controls (auth, rate limits, input validation) still pass.
  • Record final known limitations and follow-up actions.
#opennext#cloudflare#nextjs#workers#capability-pack

Source citations

Add this badge to your README

Show that OpenNext Cloudflare Capability Pack Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/skills/opennext-cloudflare-capability-pack.svg)](https://heyclau.de/entry/skills/opennext-cloudflare-capability-pack)

How it compares

OpenNext Cloudflare Capability Pack Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

2 trust signals differ across this comparison (Package trust, Source provenance).

Field
Cloudflare logoOpenNext Cloudflare Capability Pack Skill

Expert OpenNext + Cloudflare capability skill for Next.js on Workers, runtime constraints, cache strategy, and production-safe deploy architecture.

Open dossier
Cloudflare logoCloudflare Workers D1 KV R2 Capability Pack Skill

Expert Cloudflare capability skill for designing workers that combine D1, KV, and R2 with clear consistency, caching, and security boundaries.

Open dossier
Zero-Budget SaaS Launch Capability Pack Skill

Expert zero-budget launch capability pack for building and shipping SaaS using free-tier infrastructure and constrained execution plans.

Open dossier
Cloudflare logoCloudflare Workers AI Edge Functions Skill

Run AI inference and serverless functions on Cloudflare Workers AI: call hosted models like Llama, Whisper, and Stable Diffusion through the Workers AI binding, deploy with wrangler, and use D1/R2/KV storage plus the free daily Neuron allocation.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage verified2026-04-10Package verified2026-04-10Package verified2026-04-11Package verified2025-10-16
Source provenanceDiffersSource-backedNo submission linkNo submission linkNo submission link
Submitter————
Install riskReview firstLow riskLow riskLow risk
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandCloudflare logoCloudflareCloudflare logoCloudflare—Cloudflare logoCloudflare
Categoryskillsskillsskillsskills
Sourcefirst-partyfirst-partyfirst-partyfirst-party
AuthorJSONboredJSONboredJSONboredJSONbored
Added2026-04-102026-04-102026-04-112025-10-16
Platforms
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Source repo————
Safety notes✓May produce commands or configuration for live infrastructure, CI, releases, or indexing; test changes in staging or dry-run mode first. Use least-privilege API tokens and review workflow, deploy, DNS, cache, and release changes before applying them to production.✓May produce commands or configuration for live infrastructure, CI, releases, or indexing; test changes in staging or dry-run mode first. Use least-privilege API tokens and review workflow, deploy, DNS, cache, and release changes before applying them to production.✓Use this skill as planning or review guidance; verify generated commands, code, configuration, and infrastructure changes before running them. Apply least-privilege credentials and test in staging or a disposable branch before using it on production systems, CI, deployment, or account-write workflows.✓Deploying with wrangler writes Workers and bindings to your Cloudflare account; review what you deploy, since it serves live traffic. Running Workers AI models consumes paid Neurons beyond the free daily allocation; set usage expectations before deploying inference at scale.
Privacy notes✓Inputs can include repository metadata, workflow logs, deployment settings, domain names, analytics exports, and service configuration. Redact tokens, account IDs, private URLs, customer data, and proprietary deployment details before sharing generated reports or prompts.✓Inputs can include repository metadata, workflow logs, deployment settings, domain names, analytics exports, and service configuration. Redact tokens, account IDs, private URLs, customer data, and proprietary deployment details before sharing generated reports or prompts.✓Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model. Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts.✓Requests sent to Workers AI models are processed on Cloudflare's network; review what data your function forwards to the model. Keep Cloudflare API tokens in wrangler's secret store or environment variables, never hard-coded or committed.
Prerequisites
  • Next.js codebase and Cloudflare account
  • Wrangler configuration access
  • Deployment environment separation (dev/prod)
  • Cloudflare account and worker project
  • D1/KV/R2 bindings access
  • Defined data model and SLA targets
  • Product hypothesis
  • Free-tier account access
  • Launch KPI targets
  • Cloudflare account
  • Wrangler CLI 3.0+
  • Node.js 18+
  • @cloudflare/workers-types
Install
curl -L https://heyclau.de/downloads/skills/opennext-cloudflare-capability-pack.zip -o opennext-cloudflare-capability-pack.zip && unzip -o opennext-cloudflare-capability-pack.zip -d ./opennext-cloudflare-capability-pack
curl -L https://heyclau.de/downloads/skills/cloudflare-workers-d1-kv-r2-capability-pack.zip -o cloudflare-workers-d1-kv-r2-capability-pack.zip && unzip -o cloudflare-workers-d1-kv-r2-capability-pack.zip -d ./cloudflare-workers-d1-kv-r2-capability-pack
curl -L https://heyclau.de/downloads/skills/zero-budget-saas-launch-capability-pack.zip -o zero-budget-saas-launch-capability-pack.zip && unzip -o zero-budget-saas-launch-capability-pack.zip -d ./zero-budget-saas-launch-capability-pack
npm install -g wrangler
Config————
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

Cloudflare logoguides

Build Cloudflare Workers AI Agents With Durable State

Build Workers AI agents with durable session and workflow state.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by MkDev11

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.