wrangler
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Profile →npx skills add cloudflare/skills --skill wrangler --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Wrangler CLI Your knowledge of Wrangler CLI flags, config fields, and subcommands may be outdated. **Prefer retrieval over pre-training** for any Wrangler task. ## Retrieval Sources Fetch the **latest** information before writing or reviewing Wrangler commands and config. Do not rely on baked-in knowledge for CLI flags, config fields, or binding shapes. | Source | How to retrieve | Use for | |--------|----------------|---------| | Wrangler docs | `https://developers.cloudflare.com/workers/wrangler/` | CLI commands, flags, config reference | | Wrangler config schema | `node_modules/wrangler/config-schema.json` | Config fields, binding shapes, allowed values | | Cloudflare docs | Search tool or `https://developers.cloudflare.com/workers/` | API reference, compatibility dates/flags | ## FIRST: Check if Wrangler is installed, and if not, install it Check if Wrangler is installed by running: ```bash wrangler --version # Requires v4.x+ ``` If Wrangler is not installed, you should install it by running: ```bash npm install -D wrangler@latest ``` Wherever possible, you should use Wrangler instead of manually constructing API requests. ## Key Guidelines - **Use `wrangler.jsonc`**: Prefer
- Retrieval Sources
- FIRST: Check if Wrangler is installed, and if not, install it
- Key Guidelines
- Quick Start: New Worker
- Quick Reference: Core Commands
- Configuration (wrangler.jsonc)
- Minimal Config
- Full Config with Bindings
- Generate Types from Config
- Local Development
- Start Dev Server
- Remote Bindings for Local Dev
- Local Secrets
- Deployment
wrangler --version # Requires v4.x+ npm install -D wrangler@latest Initialize new project npx wrangler init my-worker Or with a framework npx create-cloudflare@latest my-app Generate worker-configuration.d.ts wrangler types Custom output path wrangler types ./src/env.d.ts
What does the wrangler skill do?
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
How do I install it?
Run `npx skills add cloudflare/skills --skill wrangler --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From cloudflare/skills, a repository with 2,539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.