Generated banner for Cloudflare
Generated logo for Cloudflare

Cloudflare

OpenAIOfficialCreated by CloudflareDistributed by OpenAI

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

From the author

Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
— the description by Cloudflare

AutoGineer summary

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

The Cloudflare platform skill provides a centralized resource for developers building on Cloudflare's edge network. It covers the full ecosystem, including compute (Workers, Pages), storage (KV, D1, R2), AI integration (Workers AI, Agents SDK), networking, and security. The skill emphasizes a retrieval-first approach, directing users to official Cloudflare documentation and configuration schemas to ensure accuracy regarding API signatures, limits, and pricing.

What it does

  • Provides decision trees to help select the right Cloudflare product for specific compute, storage, or networking needs.
  • Offers structured references for the Cloudflare Agents SDK, including lifecycle hooks and state management.
  • Guides users on integrating AI models and vector databases into edge applications.
  • Outlines methods for managing infrastructure-as-code using Terraform or Pulumi.
  • Facilitates access to product-specific documentation for security, media, and analytics services.
  • Maintains a directory of developer tools like Wrangler and Miniflare for local development and testing.

When to use it

  • When starting a new project on the Cloudflare platform and needing to choose the appropriate architecture.
  • When implementing stateful AI agents using the Cloudflare Agents SDK.
  • When configuring edge compute, storage bindings, or networking rules.
  • When troubleshooting API limits, configuration errors, or deployment issues.
  • When integrating AI models or vector search into existing edge applications.

Advantages

  • Consolidates a vast ecosystem into a navigable, task-oriented structure.
  • Promotes the use of official, up-to-date documentation over potentially stale training data.
  • Simplifies complex architectural decisions through clear, logic-based decision trees.
  • Provides specific code patterns for advanced features like Durable Objects and AI agents.
  • Supports modern infrastructure-as-code workflows for consistent deployments.

Usage examples

“I need to build a stateful AI chat agent on Cloudflare. How do I start?”
The agent will guide you to use the AIChatAgent class from the Agents SDK, explain how to manage message history, and provide a template for integrating AI models.
“Which storage solution should I use for relational data in my Worker?”
The agent will point you to D1 for SQLite-based relational storage or Hyperdrive for connecting to existing Postgres/MySQL databases.
“How do I expose my local development server to the internet via Cloudflare?”
The agent will provide instructions on using Cloudflare Tunnel to securely connect your local service to the Cloudflare edge.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/openai/cloudflare/download
  2. Unzip it into the cross-client skills folder of your project:

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

Documentation by Cloudflare

Cloudflare Platform Skill

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

Your knowledge of Cloudflare APIs, types, limits, and pricing may be outdated. Prefer retrieval over pre-training — the references in this skill are starting points, not source of truth.

Retrieval Sources

Fetch the latest information before citing specific numbers, API signatures, or configuration options. Do not rely on baked-in knowledge or these reference files alone.

SourceHow to retrieveUse for
Cloudflare docsSearch https://developers.cloudflare.com/ directlyLimits, pricing, API reference, compatibility dates/flags
Workers typesnpm pack @cloudflare/workers-types or check node_modulesType signatures, binding shapes, handler types
Wrangler config schemanode_modules/wrangler/config-schema.jsonConfig fields, binding shapes, allowed values
Product changelogshttps://developers.cloudflare.com/changelog/Recent changes to limits, features, deprecations

When a reference file and the docs disagree, trust the docs. This is especially important for: numeric limits, pricing tiers, type signatures, and configuration options.

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 analytics/metrics data"
Need analytics?
├─ Query across all Cloudflare products (HTTP, Workers, DNS, etc.) → graphql-api/
├─ Custom high-cardinality metrics from Workers → analytics-engine/
├─ Client-side (RUM) performance data → web-analytics/
├─ Workers Logs and real-time debugging → observability/
└─ Raw logs (Logpush to external tools) → Cloudflare docs
"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/
GraphQL Analytics APIreferences/graphql-api/
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/

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.

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
Cloudflare
Publisher
OpenAI (Official)
Distributed by
OpenAI
Source
openai/plugins · plugins/cloudflare/skills/cloudflare · commit d420d13
Licence
Apache License 2.0 (redistribution allowed)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

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

Download ZIP

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