Generated banner for Cloudflare Deploy
Generated logo for Cloudflare Deploy

Cloudflare Deploy

OpenAIOfficialPublished by OpenAI

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

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

Cloudflare Deploy provides a centralized framework for developers to build, host, and manage projects on Cloudflare. It covers the entire ecosystem, including serverless compute (Workers), full-stack web hosting (Pages), persistent storage (D1, R2, KV), and AI-powered agent development. The skill includes decision trees to help select the right product for specific needs, authentication guidance, and troubleshooting steps for deployment issues.

What it does

  • Provides decision trees to select the appropriate Cloudflare product for compute, storage, AI, or networking.
  • Offers guidance on authenticating with the Cloudflare platform via CLI or CI/CD.
  • Includes a comprehensive product index for quick reference to documentation.
  • Provides specific patterns and API references for building stateful AI agents using the Agents SDK.
  • Offers troubleshooting steps for network-related deployment failures.
  • Supports infrastructure-as-code integration with tools like Pulumi and Terraform.

When to use it

  • When you need to deploy, host, or publish a project to Cloudflare.
  • When you are unsure which Cloudflare service (e.g., Workers vs. Pages) best fits your application requirements.
  • When you need to build stateful, globally distributed AI agents.
  • When you encounter network errors or timeouts during the deployment process.
  • When setting up persistent storage or database solutions within the Cloudflare ecosystem.

Advantages

  • Consolidates fragmented documentation into a single, navigable resource.
  • Simplifies product selection through clear, use-case-driven decision trees.
  • Provides actionable code patterns for complex tasks like AI agent development.
  • Addresses common deployment friction points like authentication and network sandboxing.

Usage examples

“I need to deploy a full-stack web application to Cloudflare. Which service should I use?”
The agent will guide you to use Cloudflare Pages for full-stack web apps with Git-based deployments.
“How do I build an AI chat agent on Cloudflare?”
The agent will provide the Agents SDK reference, including the AIChatAgent class and examples for streaming responses and managing message history.
“My deployment is failing with a network timeout error. What should I do?”
The agent will advise you to rerun the deployment command with the sandbox_permissions=require_escalated flag to bypass network restrictions.
“How do I store relational data for my worker?”
The agent will recommend using D1 for SQLite-based relational storage or Hyperdrive for connecting to existing Postgres/MySQL databases.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/openai/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/network-interconnect/gotchas.md

CNI Gotchas & Troubleshooting

Common Errors

"Status: Pending"

Cause: Cross-connect not installed, RX/TX fibers reversed, wrong fiber type, or low light levels Solution:

  1. Verify cross-connect installed

  2. Check fiber at patch panel

  3. Swap RX/TX fibers

  4. Check light with optical power meter (target > -20 dBm)

  5. Contact account team

"Status: Unhealthy"

Cause: Physical issue, low light (<-20 dBm), optic mismatch, or dirty connectors Solution:

  1. Check physical connections

  2. Clean fiber connectors

  3. Verify optic types (10GBASE-LR/100GBASE-LR4)

  4. Test with known-good optics

  5. Check patch panel

  6. Contact account team

"BGP Session Down"

Cause: Wrong IP addressing, wrong ASN, password mismatch, or firewall blocking TCP/179 Solution:

  1. Verify IPs match CNI object

  2. Confirm ASN correct

  3. Check BGP password

  4. Verify no firewall on TCP/179

  5. Check BGP logs

  6. Review BGP timers

"Low Throughput"

Cause: MTU mismatch, fragmentation, single GRE tunnel (v1), or routing inefficiency Solution:

  1. Check MTU (1500↓/1476↑ for v1, 1500 both for v2)

  2. Test various packet sizes

  3. Add more GRE tunnels (v1)

  4. Consider upgrading to v2

  5. Review routing tables

  6. Use LACP for bundling (v1)

API Errors

400 Bad Request: "slot_id already occupied"

Cause: Another interconnect already uses this slot
Solution: Use occupied=false filter when listing slots:

await client.networkInterconnects.slots.list({
  account_id: id,
  occupied: false,
  facility: 'EWR1',
});
400 Bad Request: "invalid facility code"

Cause: Typo or unsupported facility
Solution: Check locations PDF for valid codes

403 Forbidden: "Enterprise plan required"

Cause: Account not enterprise-level
Solution: Contact account team to upgrade

422 Unprocessable: "validate_only request failed"

Cause: Dry-run validation found issues (wrong slot, invalid config)
Solution: Review error message details, fix config before real creation

Rate Limiting

Limit: 1200 requests/5min per token
Solution: Implement exponential backoff, cache slot listings

Cloud-Specific Issues

AWS Direct Connect: "VLAN not matching"

Cause: VLAN ID from AWS LOA doesn't match CNI config
Solution:

  1. Get VLAN from AWS Console after ordering

  2. Send exact VLAN to CF account team

  3. Verify match in CNI object config

AWS: "Connection stuck in Pending"

Cause: LOA not provided to CF or AWS connection not accepted
Solution:

  1. Verify AWS connection status is "Available"

  2. Confirm LOA sent to CF account team

  3. Wait for CF team acceptance (can take days)

GCP: "BGP routes not propagating"

Cause: BGP routes from GCP Cloud Router ignored by design
Solution: Use static routes in Magic WAN instead

GCP: "Cannot query VLAN attachment status via API"

Cause: GCP Cloud Interconnect Dashboard-only (no API yet)
Solution: Check status in CF Dashboard or GCP Console

Partner Interconnect Issues

Equinix: "Virtual circuit not appearing"

Cause: CF hasn't accepted Equinix connection request
Solution:

  1. Verify VC created in Equinix Fabric Portal

  2. Contact CF account team to accept

  3. Allow 2-3 business days

Console Connect/Megaport: "API creation fails"

Cause: Partner interconnects require partner portal + CF approval
Solution: Cannot fully automate. Order in partner portal, notify CF account team.

Anti-Patterns

Anti-PatternWhy BadSolution
Single interconnect for productionNo SLA, single point of failureUse ≥2 with device diversity
No backup InternetCNI fails = total outageAlways maintain alternate path
Polling status every secondRate limits, wastes API callsPoll every 30-60s max
Using v1 for Magic WAN v2 workloadsGRE overhead, complexityUse v2 for simplified routing
Assuming BGP session = traffic flowingBGP up ≠ routes installedVerify routing tables + test traffic
Not enabling maintenance alertsSurprise downtime during maintenanceEnable notifications immediately
Hardcoding VLAN in automationVLAN assigned by CF (v1)Get VLAN from CNI object response
Using Direct without colocationCan't access cross-connectUse Partner or Cloud interconnect

What's Not Queryable via API

Cannot retrieve:

  • BGP session state (use Dashboard or BGP logs)

  • Light levels (contact account team)

  • Historical metrics (uptime, traffic)

  • Bandwidth utilization per interconnect

  • Maintenance window schedules (notifications only)

  • Fiber path details

  • Cross-connect installation status

Workarounds:

  • External monitoring for BGP state

  • Log aggregation for historical data

  • Notifications for maintenance windows

Limits

Resource/LimitValueNotes
Max optical distance10kmPhysical limit
MTU (v1)1500↓ / 1476↑Asymmetric
MTU (v2)1500 bothSymmetric
GRE tunnel throughput1 GbpsPer tunnel (v1)
Recovery timeDaysNo formal SLA
Light level minimum-20 dBmTarget threshold
API rate limit1200 req/5minPer token
Health check delay6 hoursNew maintenance alert subscriptions

Requirements and compatibility

Written for: OpenAI Codex

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

Published by
OpenAI
Publisher
OpenAI (Official)
Source
openai/skills · skills/.curated/cloudflare-deploy · commit 49f948f
Licence
Apache License 2.0 (redistribution allowed)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by OpenAI.

Download ZIP

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