Cloudflare Manager

Automating Cloudflare Workers deployment with KV and R2 bindings requires provisioning namespaces and buckets then linking them to your edge application. This Skill consolidates these fragmented steps into a single repeatable workflow, handling storage binding and deployment automatically.

Yes, deploying Cloudflare Pages and configuring DNS routes can be handled in the same workflow. The Skill provisions Pages projects and sets up DNS routing alongside Workers and storage, enabling multi-service edge deployments across your accounts.

Yes, you need a valid Cloudflare API key and a Bun runtime to manage edge resources. You must configure CLOUDFLARE_API_KEY in a .env file and validate credentials before performing provisioning actions for Workers, KV, R2, Pages, and DNS.

The best way to bootstrap a new multi-account edge application is to automate resource provisioning end-to-end. This Skill standardizes environments by deploying Workers, binding KV and R2 storage, deploying Pages, and configuring DNS across multiple accounts.

Provisioning R2 buckets and KV namespaces requires appropriate API permissions for Workers, KV, R2, Pages, and DNS. Your configured CLOUDFLARE_API_KEY must possess these specific access rights to perform automated validations and resource configurations.

Edge deployment storage binding fails when credentials lack appropriate permissions for KV or R2 services. You must validate your CLOUDFLARE_API_KEY in the Bun runtime environment to ensure it has the necessary access rights for Workers storage bindings.