What problem does it solve? Managing Cloudflare accounts, Workers, R2, D1, and billing through scattered MCP configurations and ad-hoc credentials is error-prone. This Skill centralizes all Cloudflare access through Executor as the single integration, credential, and policy manager, avoiding duplicate MCP registrations across agents. ## Core Features & Use Cases - Executor-based integration routing: Discovers and calls registered Cloudflare MCP integrations (API, docs, bindings, builds, observability, GraphQL) instead of configuring direct MCP connections in each agent. - OAuth and API-token setup: Guides human-in-the-loop OAuth flows and credential handoffs through Executor's browser UI, keeping secrets out of chat, shell arguments, and logs. - R2 object operations via OAuth: Uses the existing authorized connection for bucket and object read/write/delete through REST routes discovered in Code Mode, without issuing new S3 credentials. - Billing investigation workflow: Aggregates Billable Usage API data inside Code Mode, separates fixed subscription fees from measured usage, and reports provisional subtotals with explicit uncertainty. - Use Case: A user asks why their Cloudflare bill changed. The Skill verifies the token-authenticated connection, fetches billable-usage for the current cycle, aggregates ContractedCost by service family and currency, and reports confirmed charges versus estimates. ## Quick Start Set up Cloudflare through Executor and verify my account connection with a read-only API call.