Comprehensive Cloudflare account management for deploying Workers, KV Storage, R2, Pages, DNS, and Routes. Use when deploying cloudflare services, managing worker containers, configuring KV/R2 storage, or setting up DNS/routing. Requires CLOUDFLARE_API_KEY in .env and Bun runtime with dependencies installed.
View on GitHubsecondsky/claude-skills
cloudflare-manager
January 24, 2026
Select agents to install to:
npx add-skill https://github.com/secondsky/claude-skills/blob/main/plugins/cloudflare-manager/skills/cloudflare-manager/SKILL.md -a claude-code --skill cloudflare-managerInstallation paths:
.claude/skills/cloudflare-manager/# Cloudflare Manager
Comprehensive Cloudflare service management skill that enables deployment and configuration of Workers, KV Storage, R2 buckets, Pages, DNS records, and routing. Automatically validates API credentials, extracts deployment URLs, and provides actionable error messages.
## Initial Setup
Before using this skill for the first time:
1. **Install Dependencies**
```bash
cd ~/.claude/skills/cloudflare-manager
bun install
```
2. **Configure API Key**
Create a `.env` file in your project root:
```bash
CLOUDFLARE_API_KEY=your_api_token_here
CLOUDFLARE_ACCOUNT_ID=your_account_id # Optional, auto-detected
```
**Getting your API token**:
- Visit https://dash.cloudflare.com/profile/api-tokens
- Click "Create Token"
- Use "Edit Cloudflare Workers" template (or create custom token)
- Required permissions:
- Account > Workers Scripts > Edit
- Account > Workers KV Storage > Edit
- Account > Workers R2 Storage > Edit
- Account > Cloudflare Pages > Edit
- Zone > DNS > Edit (if using custom domains)
3. **Validate Credentials**
Run validation to verify your API key and check permissions:
```bash
cd ~/.claude/skills/cloudflare-manager
bun scripts/validate-api-key.ts
```
**Expected output**:
```
✅ API key is valid!
ℹ️ Token Status: active
ℹ️ Account: Your Account Name (abc123...)
🔑 Granted Permissions:
✅ Workers Scripts: Edit
✅ Workers KV Storage: Edit
✅ Workers R2 Storage: Edit
```
**Troubleshooting validation**:
- If validation fails with 401/403: Check your API token is correct in `.env`
- If validation fails with network error: Check internet connection
- Use `--no-cache` flag to force fresh validation: `bun scripts/validate-api-key.ts --no-cache`
## Current API Permissions
<!-- PERMISSIONS_START -->
Run `bun scripts/validate-api-key.ts` to populate this section with your current permissions.
<!-- PERMISSIONS_END -->
##