cloudflare-manager

安装量: 57
排名: #13011

安装

npx skills add https://github.com/secondsky/claude-skills --skill 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: Install Dependencies cd ~/.claude/skills/cloudflare-manager bun install Configure API Key Create a .env file in your project root: 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) Validate Credentials Run validation to verify your API key and check permissions: 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 Run bun scripts/validate-api-key.ts to populate this section with your current permissions. Quick Start Guide Deploy a Worker Container To deploy a new worker container sandbox:

Using the skill

bun scripts/workers.ts deploy worker-name ./worker-script.js
What happens
:
Creates new worker container
Deploys JavaScript/TypeScript code
Automatically extracts and returns Cloudflare-generated URL (e.g.,
https://worker-name.username.workers.dev
)
Returns worker ID and configuration
Example conversation
:
User: "Set up and deploy a new cloudflare worker container sandbox named 'api-handler' and return the URL"
Claude: [Deploys worker using bun scripts/workers.ts deploy api-handler ./worker.js]
Returns URL: https://api-handler.username.workers.dev
Exit codes
:
0
Success - worker deployed and URL returned
1
Failure - check error message for details
Performance
Deployment typically completes in 2-5 seconds Create and Use KV Storage To create a KV namespace and store data:

Create namespace

bun scripts/kv-storage.ts create-namespace user-sessions

Returns: Namespace ID (e.g., abc123def456)

Save this ID for binding to workers

Write key-value pair

bun scripts/kv-storage.ts write < namespace-id

"session:user123" '{"userId":"123","token":"abc"}'

Read value

bun scripts/kv-storage.ts read < namespace-id

"session:user123"

Returns:

List all keys (useful for debugging)

bun scripts/kv-storage.ts list-keys < namespace-id

Delete a key

bun scripts/kv-storage.ts delete
<
namespace-id
>
"session:user123"
Important
KV storage uses eventual consistency. Writes may take up to 60 seconds to propagate globally. For immediate reads, use the same edge location where you wrote the data. Create R2 Bucket and Upload Files To create an R2 bucket and manage objects:

Create bucket

bun scripts/r2-storage.ts create-bucket media-assets

Upload file

bun scripts/r2-storage.ts upload media-assets ./images/logo.png logo.png

List objects

bun scripts/r2-storage.ts list-objects media-assets

Download object

bun scripts/r2-storage.ts download media-assets logo.png ./downloaded-logo.png Deploy to Cloudflare Pages To deploy a static site or application to Pages:

Create Pages project (or get existing project info)

bun scripts/pages.ts deploy my-app ./dist

Returns: https://my-app.pages.dev

Set environment variable

bun scripts/pages.ts set-env my-app API_URL https://api.example.com

Set environment variable for specific environment

bun scripts/pages.ts set-env my-app DEBUG true --env preview

Get deployment URL

bun scripts/pages.ts get-url my-app
Auto-extracted URLs
The Pages script automatically extracts and returns the Cloudflare-generated URL (e.g.,
https://my-app.pages.dev
) from the deployment response.
Note
The API creates the project structure, but for actual file uploads, you'll need Wrangler CLI:
bunx wrangler pages deploy ./dist --project-name
=
my-app
Why this works
The skill creates/verifies the Pages project and returns the URL. For the initial deployment with files, Wrangler handles the complex multipart upload process. Configure DNS and Routes To create DNS records and configure worker routes:

Create DNS A record

bun scripts/dns-routes.ts create-dns example.com A api 192.168 .1.1

Route pattern to worker

bun scripts/dns-routes.ts create-route example.com ".example.com/api/" api-handler Common Workflows Multi-Service Setup To set up a complete application with worker, KV storage, and R2 bucket: Create KV namespace for caching bun scripts/kv-storage.ts create-namespace app-cache Create R2 bucket for media bun scripts/r2-storage.ts create-bucket app-media Deploy worker with bindings bun scripts/workers.ts deploy app-worker ./worker.js --kv-binding app-cache --r2-binding app-media Configure route bun scripts/dns-routes.ts create-route example.com "example.com/*" app-worker Update Worker Configuration To update an existing worker's code or bindings:

Update worker code

bun scripts/workers.ts update worker-name ./new-worker-script.js

Get worker details

bun scripts/workers.ts get worker-name

List all workers

bun scripts/workers.ts list Bulk KV Operations To perform bulk operations on KV storage:

Bulk write from JSON file

bun scripts/kv-storage.ts bulk-write namespace-name ./data.json

Delete multiple keys

bun scripts/kv-storage.ts bulk-delete namespace-name key1 key2 key3
Error Handling
Missing API Key
If
.env
file is missing or
CLOUDFLARE_API_KEY
is not set:
Error: CLOUDFLARE_API_KEY not found in environment
Solution: Create .env file in project root:
echo "CLOUDFLARE_API_KEY=your_token_here" > .env
Invalid Permissions
If API token lacks required permissions:
Error: Insufficient permissions for Workers deployment
Required: Workers Scripts: Edit
Current: Workers Scripts: Read
Solution: Update token permissions at:
https://dash.cloudflare.com/profile/api-tokens
API Rate Limiting
If too many requests are made:
Error: Rate limit exceeded (429)
Solution: Retry automatically with exponential backoff (3 attempts)
Network Issues
If API is unreachable:
Error: Failed to connect to Cloudflare API
Solution: Check internet connection and retry
Best Practices
Security
:
Never commit
.env
files - always add to
.gitignore
Use token-based authentication (not API keys)
Rotate tokens periodically (every 90 days recommended)
Use least-privilege principle: only grant required permissions
Store secrets via Wrangler CLI:
wrangler secret put SECRET_NAME
Performance
:
Deploy workers to minimize latency (they run at Cloudflare edge)
Use KV storage for frequently-read data (not frequently-written)
Use R2 for large files (KV has 25MB limit per key)
Enable caching with appropriate TTLs
Keep worker scripts under 1MB for faster cold starts
Development Workflow
:
Test locally first:
wrangler dev
for local testing
Use staging environment before production
Validate credentials after token updates:
bun scripts/validate-api-key.ts
Monitor worker logs:
wrangler tail worker-name
Version your workers: use names like
api-v1
,
api-v2
Naming Conventions
:
Workers: Use descriptive names (e.g.,
user-auth-worker
not
worker1
)
KV namespaces: Include purpose (e.g.,
app-sessions
,
api-cache
)
R2 buckets: Use lowercase with hyphens (e.g.,
media-assets-prod
)
Be consistent across your infrastructure
Resource Management
:
Delete unused workers, namespaces, and buckets
Monitor usage in Cloudflare dashboard
Free tier limits: 100,000 requests/day for Workers
Set up billing alerts to avoid surprises
Advanced Usage
For advanced scenarios including:
Complex routing configurations
Multi-region deployments
Custom domain setup
Worker-to-worker communication
Durable Objects integration
Bulk operations and migrations
See
examples.md
for comprehensive examples and patterns.
Script Reference
All scripts are located in
~/.claude/skills/cloudflare-manager/scripts/
:
validate-api-key.ts
Validate API credentials and display permissions
workers.ts
Deploy, update, and manage Workers
kv-storage.ts
Create and manage KV namespaces and key-value pairs
r2-storage.ts
Create and manage R2 buckets and objects
pages.ts
Deploy and configure Cloudflare Pages projects
dns-routes.ts
Configure DNS records and worker routes
utils.ts
Shared utilities for API calls and error handling
Templates
Starter templates are available in
~/.claude/skills/cloudflare-manager/templates/
:
worker-template.js
Basic worker template with fetch handler
wrangler.toml.template
Wrangler configuration template
Troubleshooting
Common Issues and Solutions
Issue
"Worker deployment failed with unknown error"
Symptoms
Deployment command exits with error code 1, no specific error message
Solutions
:
Check script syntax:
node --check ./worker.js
Verify file exists:
ls -lh ./worker.js
Re-validate API key:
bun scripts/validate-api-key.ts --no-cache
Check worker name is valid (alphanumeric, hyphens, underscores only)
Issue
"KV namespace not found"
Symptoms
Error when trying to read/write to namespace
Solutions
:
List all namespaces:
bun scripts/kv-storage.ts list-namespaces
Verify you're using namespace ID (not name) in commands
Check namespace wasn't deleted
Ensure API token has KV Storage permissions
Issue
"R2 bucket already exists" or "Bucket name taken"
Symptoms
Cannot create bucket with chosen name
Solutions
:
Bucket names must be globally unique across all Cloudflare accounts
Try a more specific name:
my-app-media-2024
instead of
media
Use existing bucket:
bun scripts/r2-storage.ts list-buckets
Names must be 3-63 characters, lowercase letters/numbers/hyphens only
Issue
"Pages deployment timeout" or "Deployment pending"
Symptoms
Deployment doesn't complete, stays in pending state
Solutions
:
Check deployment status:
bun scripts/pages.ts list-deployments project-name
View in dashboard:
https://dash.cloudflare.com/pages
Large deployments (>1000 files) may take 5-10 minutes
Cancel and retry if stuck: Delete project and recreate
Issue
"DNS record creation failed"
Symptoms
Cannot create DNS records or routes
Solutions
:
Verify zone exists:
bun scripts/dns-routes.ts list-zones
Ensure domain is added to Cloudflare and active
Check nameservers point to Cloudflare:
dig NS yourdomain.com
Verify API token has Zone > DNS > Edit permission
Issue
"API rate limit exceeded (429)"
Symptoms
Commands fail with "Too many requests"
Solutions
:
Scripts automatically retry with exponential backoff
Wait 1-2 minutes before retrying manually
Reduce concurrent operations
Rate limits: 1200 requests per 5 minutes
Issue
"CLOUDFLARE_API_KEY not found in environment"
Symptoms
Commands fail immediately with environment error Solutions : Create .env file in project root (not skill directory) Verify file content: cat .env | grep CLOUDFLARE_API_KEY Ensure no extra spaces: CLOUDFLARE_API_KEY=token (no spaces around = ) Run commands from project root where .env exists Quick Fix : cd /path/to/your/project echo "CLOUDFLARE_API_KEY=your_token_here"

.env bun scripts/validate-api-key.ts Security Notes API keys are never logged or displayed in output All API requests use HTTPS User inputs are validated before API calls Destructive operations (delete) require confirmation Permissions are cached for 24 hours to minimize token exposure Additional Resources Cloudflare API Documentation: https://developers.cloudflare.com/api/ Workers Documentation: https://developers.cloudflare.com/workers/ KV Storage Guide: https://developers.cloudflare.com/kv/ R2 Storage Guide: https://developers.cloudflare.com/r2/ Pages Documentation: https://developers.cloudflare.com/pages/

返回排行榜