wrangler
Deploy Cloudflare Workers with Wrangler CLI
Also available from: Dicklesworthstone
Cloudflare Workers deployment requires understanding of CLI commands, configuration, and resource bindings. This skill provides comprehensive documentation for deploying and managing Workers, KV, R2, D1, and more.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "wrangler". How do I deploy my Worker?
Expected outcome:
- Run these commands:
- 1. wrangler deploy - Deploy to production
- 2. wrangler deploy --env staging - Deploy to staging environment
- 3. wrangler deploy --dry-run - Validate without deploying
- Make sure to run wrangler check first to validate your config.
Using "wrangler". How do I add a KV namespace?
Expected outcome:
- 1. Create namespace: wrangler kv namespace create MY_KV
- 2. Add to wrangler.jsonc:
- { "kv_namespaces": [{ "binding": "KV", "id": "<ID>" }] }
- 3. Run wrangler types to update TypeScript bindings
Security Audit
SafeAll 161 static findings are false positives. The skill is official Cloudflare documentation for the Wrangler CLI tool. External command detections are legitimate CLI commands documented in code blocks. Network detections are official Cloudflare URLs and localhost testing endpoints. Environment variable access is standard secret management documentation. No malicious behavior detected.
Risk Factors
⚙️ External commands (133)
🌐 Network access (3)
🔑 Env variables (6)
Detected Patterns
Quality Score
What You Can Build
Deploy a new Worker to Cloudflare
Get step-by-step guidance for initializing and deploying a new Worker with proper configuration
Configure KV and R2 storage bindings
Learn how to set up key-value storage and object storage for your Worker
Manage secrets for production Workers
Securely manage API keys and secrets using wrangler secret commands
Try These Prompts
How do I deploy my Worker to Cloudflare using wrangler?
Show me how to add a KV namespace binding to my wrangler.jsonc config
How do I securely add API keys as secrets for my Worker?
How do I test my Worker locally with remote R2 and AI bindings?
Best Practices
- Run wrangler check before every deployment to catch configuration errors
- Use wrangler types after any config changes to regenerate TypeScript bindings
- Set compatibility_date to a recent date within 30 days for latest features
Avoid
- Hardcoding secrets directly in wrangler.jsonc - use wrangler secret instead
- Skipping wrangler types after adding new bindings
- Deploying without testing locally first using wrangler dev