wrangler

Run and troubleshoot Wrangler CLI commands for Cloudflare Worker development and deployment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Wrangler CLI flags and configuration fields change frequently, so relying on memorized syntax leads to broken deployments, misconfigured bindings, and accidental overwrites of dashboard settings. This Skill grounds every command and config edit in the project's installed Wrangler version and current official documentation. ## Core Features & Use Cases - Project Inspection: Detects the package manager, installed Wrangler version, framework, and active config file before running any command, so commands always use the project's local Wrangler version. - Documentation-Grounded Commands: Maps each task (deployments, secrets, environments, bindings, rollbacks, migrations) to the correct official Cloudflare docs page or local wrangler --help output. - Safe Change Application: Covers environment inheritance, secret handling, dashboard reconciliation, Vite plugin environments, and rollback limitations to prevent destructive mistakes. - Validation Workflow: Regenerates TypeScript types with wrangler types and uses wrangler deploy --dry-run to verify builds before deployment. - Use Case: You need to add a KV binding to a Worker's staging environment. The Skill checks environment inheritance in your wrangler.jsonc, verifies the binding identifier to avoid automatic provisioning, and validates with a dry-run deploy. ## Quick Start Use the wrangler skill to deploy my Worker to the staging environment and verify the configuration first.

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 the project's build workflow followed by `wrangler deploy` through the project's package scripts so it uses the local Wrangler version. Validate first with `wrangler deploy --dry-run` using the intended config and environment.

How do I set secrets for a Cloudflare Worker?▼

Set Worker secrets with `wrangler secret put`, keeping values out of command arguments, source code, and logs by using interactive input or protected stdin. Note that `secret put` deploys immediately; use `wrangler versions secret` when the change must be staged.

Does Wrangler config apply to staging and production environments separately?▼

Wrangler environments do not fully inherit all fields, so some bindings and variables must be specified separately per environment. A working default config does not establish that staging is configured; check environment inheritance before adding bindings.

Why does Wrangler overwrite my dashboard settings on deploy?▼

Wrangler can overwrite dashboard variables and routes because the config file is the source of truth during deployment. Reconcile dashboard changes with the config before deploying, and verify resource identifiers to avoid automatic provisioning of new resources.

What are the limitations of Wrangler rollback?▼

Wrangler rollback restores Worker code to a previous version but does not roll back connected resources or their data. Check the rollback limitations documentation before reverting deployments that interact with KV, D1, or other bindings.