cloudflare

Purpose

This skill provides programmatic access to Cloudflare's API for managing DNS records, zones, Pages sites, Access policies, Workers scripts, and R2 storage. It uses the specified account ID (YOUR_CLOUDFLARE_ACCOUNT_ID) to perform operations securely.

When to Use

Use this skill for automating infrastructure tasks like updating DNS records during deployments, securing applications with Access, deploying static sites via Pages, running edge compute with Workers, managing object storage in R2, or creating/deleting zones. Apply it in scripts, CI/CD pipelines, or when integrating Cloudflare with other services.

Key Capabilities

• DNS: Manage records (A, CNAME, TXT) within zones.
• Zones: Create, list, update, or delete zones using the account ID.
• Pages: Deploy and manage static sites with custom domains.
• Access: Enforce policies for authentication and authorization.
• Workers: Script edge logic for requests and responses.
• R2: Handle object storage operations like uploads and deletions. Authentication requires an API token set as $CLOUDFLARE_API_TOKEN; include the account ID in API requests.

Usage Patterns

Always authenticate requests with $CLOUDFLARE_API_TOKEN. Use HTTP headers for API calls (e.g., Authorization: Bearer $CLOUDFLARE_API_TOKEN). For CLI, install Wrangler and log in with wrangler login. Structure requests with JSON payloads and handle responses via status codes. Prefix API endpoints with https://api.cloudflare.com/client/v4 and include the account ID in paths, like /accounts/YOUR_CLOUDFLARE_ACCOUNT_ID/zones.