AutoGineer
Generated banner for Cloudflare Deploy
Generated logo for Cloudflare Deploy

Cloudflare Deploy

JetBrainsOfficialCreated by OpenAIDistributed by JetBrains

  • Skill
  • Tool integration
  • Cloud and DevOps
  • Apache-2.0
  • Medium risk
Download ZIP

From the author

Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
— the description by OpenAI

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The Cloudflare Deploy skill serves as a centralized hub for developers working within the Cloudflare ecosystem. It provides structured decision trees to help users select the appropriate Cloudflare product—ranging from compute and storage to AI and security—and offers guidance on authentication, deployment, and troubleshooting. The skill includes specific references for building stateful, distributed AI agents using the Cloudflare Agents SDK, covering lifecycle hooks, state management, and SQL integration.

What it does

  • Provides decision trees to select the right Cloudflare product for compute, storage, AI, or networking needs.
  • Offers guidance on authentication using Wrangler for local and CI/CD environments.
  • Includes detailed documentation for building stateful AI agents with the Cloudflare Agents SDK.
  • Supports infrastructure-as-code integration via Pulumi and Terraform.
  • Provides troubleshooting steps for network-related deployment failures.
  • Maps specific use cases to relevant product references and technical documentation.

When to use it

  • When you need to deploy, host, or publish a project on Cloudflare.
  • When you are unsure which Cloudflare product best fits your compute, storage, or AI requirements.
  • When building stateful AI agents that require persistent memory and real-time connections.
  • When you need to configure security, networking, or media optimization services on Cloudflare.
  • When troubleshooting deployment timeouts or network connectivity issues.

Advantages

  • Consolidates fragmented documentation into a single, navigable resource.
  • Simplifies product selection through clear, logic-based decision trees.
  • Provides ready-to-use code patterns for complex tasks like AI agent development.
  • Addresses common operational hurdles like authentication and network sandboxing.

Usage examples

“I need to deploy a full-stack web application to Cloudflare. Which product should I use?”
The agent will guide you to use Cloudflare Pages for Git-based deployments and provide the necessary steps to get started.
“How do I build a stateful AI chat agent on Cloudflare?”
The agent will provide the AIChatAgent class structure, explain how to manage message history, and show how to integrate with Workers AI.
“My deployment is failing with a network timeout. What should I do?”
The agent will recommend rerunning the deployment with escalated permissions using the sandbox_permissions=require_escalated flag.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/jetbrains/cloudflare-deploy/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip cloudflare-deploy.zip -d .agents/skills

Documentation by OpenAI

Cloudflare Deploy

Consolidated skill for building on the Cloudflare platform. Use decision trees below to find the right product, then load detailed references.

Prerequisites

  • When sandboxing blocks the deployment network calls, rerun with sandbox_permissions=require_escalated.

  • The deployment might take a few minutes. Use appropriate timeout values.

Authentication (Required Before Deploy)

Verify auth before wrangler deploy, wrangler pages deploy, or npm run deploy:

npx wrangler whoami    # Shows account if authenticated

Not authenticated? → references/wrangler/auth.md

  • Interactive/local: wrangler login (one-time OAuth)

  • CI/CD: Set CLOUDFLARE_API_TOKEN env var

Quick Decision Trees

"I need to run code"
Need to run code?
├─ Serverless functions at the edge → workers/
├─ Full-stack web app with Git deploys → pages/
├─ Stateful coordination/real-time → durable-objects/
├─ Long-running multi-step jobs → workflows/
├─ Run containers → containers/
├─ Multi-tenant (customers deploy code) → workers-for-platforms/
├─ Scheduled tasks (cron) → cron-triggers/
├─ Lightweight edge logic (modify HTTP) → snippets/
├─ Process Worker execution events (logs/observability) → tail-workers/
└─ Optimize latency to backend infrastructure → smart-placement/
"I need to store data"
Need storage?
├─ Key-value (config, sessions, cache) → kv/
├─ Relational SQL → d1/ (SQLite) or hyperdrive/ (existing Postgres/MySQL)
├─ Object/file storage (S3-compatible) → r2/
├─ Message queue (async processing) → queues/
├─ Vector embeddings (AI/semantic search) → vectorize/
├─ Strongly-consistent per-entity state → durable-objects/ (DO storage)
├─ Secrets management → secrets-store/
├─ Streaming ETL to R2 → pipelines/
└─ Persistent cache (long-term retention) → cache-reserve/
"I need AI/ML"
Need AI?
├─ Run inference (LLMs, embeddings, images) → workers-ai/
├─ Vector database for RAG/search → vectorize/
├─ Build stateful AI agents → agents-sdk/
├─ Gateway for any AI provider (caching, routing) → ai-gateway/
└─ AI-powered search widget → ai-search/
"I need networking/connectivity"
Need networking?
├─ Expose local service to internet → tunnel/
├─ TCP/UDP proxy (non-HTTP) → spectrum/
├─ WebRTC TURN server → turn/
├─ Private network connectivity → network-interconnect/
├─ Optimize routing → argo-smart-routing/
├─ Optimize latency to backend (not user) → smart-placement/
└─ Real-time video/audio → realtimekit/ or realtime-sfu/
"I need security"
Need security?
├─ Web Application Firewall → waf/
├─ DDoS protection → ddos/
├─ Bot detection/management → bot-management/
├─ API protection → api-shield/
├─ CAPTCHA alternative → turnstile/
└─ Credential leak detection → waf/ (managed ruleset)
"I need media/content"
Need media?
├─ Image optimization/transformation → images/
├─ Video streaming/encoding → stream/
├─ Browser automation/screenshots → browser-rendering/
└─ Third-party script management → zaraz/
"I need infrastructure-as-code"
Need IaC? → pulumi/ (Pulumi), terraform/ (Terraform), or api/ (REST API)

Product Index

Compute & Runtime
ProductReference
Workersreferences/workers/
Pagesreferences/pages/
Pages Functionsreferences/pages-functions/
Durable Objectsreferences/durable-objects/
Workflowsreferences/workflows/
Containersreferences/containers/
Workers for Platformsreferences/workers-for-platforms/
Cron Triggersreferences/cron-triggers/
Tail Workersreferences/tail-workers/
Snippetsreferences/snippets/
Smart Placementreferences/smart-placement/
Storage & Data
ProductReference
KVreferences/kv/
D1references/d1/
R2references/r2/
Queuesreferences/queues/
Hyperdrivereferences/hyperdrive/
DO Storagereferences/do-storage/
Secrets Storereferences/secrets-store/
Pipelinesreferences/pipelines/
R2 Data Catalogreferences/r2-data-catalog/
R2 SQLreferences/r2-sql/
AI & Machine Learning
ProductReference
Workers AIreferences/workers-ai/
Vectorizereferences/vectorize/
Agents SDKreferences/agents-sdk/
AI Gatewayreferences/ai-gateway/
AI Searchreferences/ai-search/
Networking & Connectivity
ProductReference
Tunnelreferences/tunnel/
Spectrumreferences/spectrum/
TURNreferences/turn/
Network Interconnectreferences/network-interconnect/
Argo Smart Routingreferences/argo-smart-routing/
Workers VPCreferences/workers-vpc/
Security
ProductReference
WAFreferences/waf/
DDoS Protectionreferences/ddos/
Bot Managementreferences/bot-management/
API Shieldreferences/api-shield/
Turnstilereferences/turnstile/
Media & Content
ProductReference
Imagesreferences/images/
Streamreferences/stream/
Browser Renderingreferences/browser-rendering/
Zarazreferences/zaraz/
Real-Time Communication
ProductReference
RealtimeKitreferences/realtimekit/
Realtime SFUreferences/realtime-sfu/
Developer Tools
ProductReference
Wranglerreferences/wrangler/
Miniflarereferences/miniflare/
C3references/c3/
Observabilityreferences/observability/
Analytics Enginereferences/analytics-engine/
Web Analyticsreferences/web-analytics/
Sandboxreferences/sandbox/
Workerdreferences/workerd/
Workers Playgroundreferences/workers-playground/
Infrastructure as Code
ProductReference
Pulumireferences/pulumi/
Terraformreferences/terraform/
APIreferences/api/
Other Services
ProductReference
Email Routingreferences/email-routing/
Email Workersreferences/email-workers/
Static Assetsreferences/static-assets/
Bindingsreferences/bindings/
Cache Reservereferences/cache-reserve/

Troubleshooting

Escalated Network Access

If deployment fails due to network issues (timeouts, DNS errors, connection resets), rerun the deploy with escalated permissions (use sandbox_permissions=require_escalated). The deploy requires escalated network access when sandbox networking blocks outbound requests.

Example guidance to the user:

The deploy needs escalated network access to deploy to Cloudflare. I can rerun the command with escalated permissions—want me to proceed?

Files

references/bindings/gotchas.md

Binding Gotchas and Troubleshooting

Critical: Global Scope Mutation

❌ THE #1 GOTCHA: Caching env in Global Scope
// ❌ DANGEROUS - env cached at deploy time
const apiKey = env.API_KEY;  // ERROR: env not available in global scope

export default {
  async fetch(request: Request, env: Env) {
    // Uses undefined or stale value!
  }
}

Why it breaks:

  • env not available in global scope

  • If using workarounds, secrets may not update without redeployment

  • Leads to "Cannot read property 'X' of undefined" errors

✅ Always access env per-request:

export default {
  async fetch(request: Request, env: Env) {
    const apiKey = env.API_KEY;  // Fresh every request
  }
}

Common Errors

"env.MY_KV is undefined"

Cause: Name mismatch or not configured
Solution: Check wrangler.jsonc (case-sensitive), run npx wrangler types, verify npx wrangler kv namespace list

"Property 'MY_KV' does not exist on type 'Env'"

Cause: Types not generated
Solution: npx wrangler types

"preview_id is required for --remote"

Cause: Missing preview binding
Solution: Add "preview_id": "dev-id" or use npx wrangler dev (local mode)

"Secret updated but Worker still uses old value"

Cause: Cached in global scope or not redeployed
Solution: Avoid global caching, redeploy after secret change

"KV get() returns null for existing key"

Cause: Eventual consistency (60s), wrong namespace, wrong environment
Solution:

# Check key exists
npx wrangler kv key get --binding=MY_KV "your-key"

# Verify namespace ID
npx wrangler kv namespace list

# Check environment
npx wrangler deployments list
"D1 database not found"

Solution: npx wrangler d1 list, verify ID in wrangler.jsonc

"Service binding returns 'No such service'"

Cause: Target Worker not deployed, name mismatch, environment mismatch
Solution:

# List deployed Workers
npx wrangler deployments list --name=target-worker

# Check service binding config
cat wrangler.jsonc | grep -A2 services

# Deploy target first
cd ../target-worker && npx wrangler deploy
"Rate limit exceeded" on KV writes

Cause: >1 write/second per key
Solution: Use different keys, Durable Objects, or Queues

Type Safety Gotchas

Missing @cloudflare/workers-types

Error: Cannot find name 'Request'
Solution: npm install -D @cloudflare/workers-types, add to tsconfig.json "types"

Binding Type Mismatches
// ❌ Wrong - KV returns string | null
const value: string = await env.MY_KV.get('key');

// ✅ Handle null
const value = await env.MY_KV.get('key');
if (!value) return new Response('Not found', { status: 404 });

Environment Gotchas

Wrong Environment Deployed

Solution: Check npx wrangler deployments list, use --env flag

Secrets Not Per-Environment

Solution: Set per environment: npx wrangler secret put API_KEY --env staging

Development Gotchas

wrangler dev vs deploy:

  • dev: Uses preview_id or local bindings, secrets not available

  • deploy: Uses production id, secrets available

Access secrets in dev: npx wrangler dev --remote
Persist local data: npx wrangler dev --persist

Performance Gotchas

Sequential Binding Calls
// ❌ Slow
const user = await env.DB.prepare('...').first();
const config = await env.MY_KV.get('config');

// ✅ Parallel
const [user, config] = await Promise.all([
  env.DB.prepare('...').first(),
  env.MY_KV.get('config')
]);

Security Gotchas

❌ Secrets in logs: console.log('Key:', env.API_KEY) - visible in dashboard
✅ console.log('Key:', env.API_KEY ? '***' : 'missing')

❌ Exposing env: return Response.json(env) - exposes all bindings
✅ Never return env object in responses

Limits Reference

ResourceLimitImpactPlan
Bindings per Worker64 totalAll binding types combinedAll
Environment variables64 max, 5KB eachPer WorkerAll
Secret size1KBPer secretAll
KV key size512 bytesUTF-8 encodedAll
KV value size25 MBPer valueAll
KV writes per key1/secondPer key; exceeding = 429 errorAll
KV list() results1000 keysPer call; use cursor for moreAll
KV operations1000 reads/dayFree tier onlyFree
R2 object size5 TBPer objectAll
R2 operations1M Class A/month freeWritesAll
D1 database size10 GBPer databaseAll
D1 rows per query100,000Result set limitAll
D1 databases10Free tierFree
Queue batch size100 messagesPer consumer batchAll
Queue message size128 KBPer messageAll
Service binding callsUnlimitedCounts toward CPU timeAll
Durable Objects1M requests/month freeFirst 1MFree

Debugging Tips

# Check configuration
npx wrangler deploy --dry-run       # Validate config without deploying
npx wrangler kv namespace list      # List KV namespaces
npx wrangler secret list            # List secrets (not values)
npx wrangler deployments list       # Recent deployments

# Inspect bindings
npx wrangler kv key list --binding=MY_KV
npx wrangler kv key get --binding=MY_KV "key-name"
npx wrangler r2 object get my-bucket/file.txt
npx wrangler d1 execute my-db --command="SELECT * FROM sqlite_master"

# Test locally
npx wrangler dev                  # Local mode
npx wrangler dev --remote         # Production bindings
npx wrangler dev --persist        # Persist data across restarts

# Verify types
npx wrangler types
cat .wrangler/types/runtime.d.ts | grep "interface Env"

# Debug specific binding issues
npx wrangler tail                 # Stream logs in real-time
npx wrangler tail --format=pretty # Formatted logs

See Also

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Node.js

Security

What our scanner noticed· Medium risk

  • Possible data-exfiltration endpoints
  • Instructions that use the network
  • Downloads piped into a shell

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
OpenAI
Publisher
JetBrains (Official)
Distributed by
JetBrains
Source
JetBrains/skills · cloudflare-deploy · commit 3f53782
Licence
Apache License 2.0 (redistribution allowed)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by OpenAI or JetBrains.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download cloudflare-deploy.zip