cloudflare-manager

Manage Cloudflare Workers, KV, R2, Pages, and DNS deployments.

1|1|Updated Dec 29, 2025

Search Tags:#deployment #cloudflare #r2 #workers #dns #kv #pages

Ready to run

npx skills add https://github.com/JoaquimCassano/ideas-marketplace --skill cloudflare-manager-joaquimcassano

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cloudflare-manager
Source: https://github.com/JoaquimCassano/ideas-marketplace/tree/main/.claude/skills/cloudflare-manager
Command: npx skills add https://github.com/JoaquimCassano/ideas-marketplace --skill cloudflare-manager-joaquimcassano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dotenv, node-fetch, and includes scripts (resource) components.

What problem does it solve?

Cloudflare management across multiple services (Workers, KV, R2, Pages, DNS) is complex and error-prone when done ad hoc; this skill centralizes deployment and configuration into a single workflow to streamline cloudflare operations.

Core Features & Use Cases

Workers deployment with automatic URL extraction and script binding support
KV and R2 provisioning, namespace binding, and object/storage management
Pages deployment with environment configuration and DNS/routing integration
API credential validation, robust error handling, and end-to-end multi-service workflows
Use cases include deploying a full application stack (worker + KV + R2 + Pages) with domain routing

Quick Start

Install dependencies, configure CLOUDFLARE_API_KEY in your project root, validate credentials, and begin deploying services with the provided scripts.

Frequently Asked Questions about cloudflare-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I deploy Cloudflare Workers, KV, R2, and Pages together in a single workflow?▼

Deploy Cloudflare services together by consolidating Workers, KV, R2, and Pages configuration under a single interface. This workflow handles credential validation, namespace binding, and routing setup to streamline multi-service application stack deployments.

What is the best way to manage Cloudflare DNS routing for a deployed Pages application?▼

Manage Cloudflare DNS routing by integrating domain configuration directly into the Pages deployment workflow. This approach configures routing rules and environment-specific settings during the deployment process to ensure proper domain resolution across production and preview environments.

Can I deploy to Cloudflare preview environments using an API token?▼

Yes, you can deploy to Cloudflare preview environments using token-based authentication. The workflow enforces API credential validation and permission checks before executing environment-specific deployments, ensuring secure access to both production and preview environments.

Do I need to manually configure R2 storage buckets before binding them to a Worker?▼

No, you do not need to manually configure R2 buckets beforehand. The deployment workflow handles R2 provisioning, object storage management, and namespace binding automatically as part of the end-to-end multi-service setup process.

Why does my Cloudflare multi-service deployment fail with a permissions error?▼

Cloudflare multi-service deployments fail with permissions errors when the provided API token lacks sufficient privileges. The workflow performs credential validation and permission checks before deployment, rejecting tokens that do not have the required access rights for Workers, KV, R2, or Pages.

Are environment variables required for Cloudflare Pages deployment scripts?▼

Yes, environment variables are required for Cloudflare Pages deployment scripts. You must configure CLOUDFLARE_API_KEY in your project root and install dependencies like dotenv to manage credentials before validating and beginning service deployments.