wrangler

Deploys and manages Cloudflare Workers and bindings via the Wrangler CLI.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/vesviet/agent-skills --skill wrangler-vesviet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wrangler
Source: https://github.com/vesviet/agent-skills/tree/main/core/skills/platform/wrangler
Command: npx skills add https://github.com/vesviet/agent-skills --skill wrangler-vesviet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Configuring and deploying Cloudflare Workers involves many CLI flags, binding types, and config fields that change frequently, and outdated knowledge leads to broken deployments, leaked secrets, or misconfigured environments. ## Core Features & Use Cases - Worker Deployment & Versioning: Deploy to staging and production with the version-then-promote pattern (wrangler versions upload then wrangler deployments create) for rolling updates and instant rollbacks. - Binding & Secret Management: Configure KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Queues, and other bindings in wrangler.jsonc, and manage secrets safely via wrangler secret put. - Type Generation & Local Dev: Generate TypeScript types with wrangler types and test locally with wrangler dev, with explicit guidance on v4 local-mode defaults. - Use Case: You are setting up a new Worker with a D1 database and KV cache. The skill guides you to declare bindings in wrangler.jsonc, set a recent compatibility date, generate types, test locally, and deploy to staging before production. ## Quick Start Use the wrangler skill to set up a new Cloudflare Worker project with a D1 binding and deploy it to staging.

Frequently Asked Questions about wrangler

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

FAQPage Schema
How do I deploy a Cloudflare Worker with Wrangler?▼

Deploy a Cloudflare Worker by running wrangler deploy after configuring wrangler.jsonc with your bindings and a recent compatibility date. For safer rollouts, upload a version with wrangler versions upload, then promote it with wrangler deployments create to enable instant rollbacks.

How do I manage secrets in Cloudflare Workers?▼

Manage secrets using wrangler secret put, which accepts interactive input, file streams, or environment variables in secure build runs. Never pass secret values as CLI arguments or commit .dev.vars or .env files, since they can leak into shell history or the repository.

Does wrangler dev run against production resources by default?▼

No, in Wrangler v4 wrangler dev defaults to local mode with simulated storage. Pass the --remote flag explicitly to bind against real production D1, R2, or KV resources, and update any CI runbooks that assumed remote was the default.

Should I use wrangler.jsonc or wrangler.toml for configuration?▼

Prefer wrangler.jsonc over TOML configuration files. After changing the config, regenerate TypeScript types with wrangler types so your Env interface stays in sync with declared bindings instead of maintaining it by hand.

Why did my Wrangler deployment go straight to production without staging?▼

A single wrangler deploy ships to the default environment, which may be production. Define environments such as env.staging and env.production in your config, deploy to staging first, and require verification before promoting to production.