What problem does it solve? Operating Cloudflare Pages from an agent requires juggling two interfaces — the Wrangler CLI for common tasks and the REST API for everything else — plus strict credential handling rules. This Skill encodes that entire workflow so an agent can create projects, deploy builds, manage custom domains, and poll deployment status without guessing commands, hand-rolling multipart uploads, or leaking tokens. ## Core Features & Use Cases - CLI-first operations: Create projects and deploy build directories with validated Wrangler commands (pages project create, pages deploy), running headlessly via CLOUDFLARE_API_TOKEN + CLOUDFLARE_ACCOUNT_ID — never wrangler login. - REST long tail: Resolve any of 20 Pages operations (domains, deployments, rollback, retry, build-cache purge) from a bundled OpenAPI slice using an endpoint index and a $ref-resolver script, so the full spec never enters context. - Deployment status tracking: Poll the deploy stage machine (queued → initialize → clone_repo → build → deploy) until success or failure, checking the {success, errors, messages, result} envelope rather than HTTP status alone. - Use Case: Ask the agent to deploy ./dist to a Pages project and add a custom domain — it runs the deploy script, captures the deployment id via deployment list --json, polls status, and registers the domain over REST. ## Quick Start Deploy my built ./dist directory to my Cloudflare Pages project and tell me when the deployment reaches success.
