Back to catalog / Developer tools
Wrangler: identify project config and target environment before commands
Distinguish local Wrangler, cf CLI, local/remote bindings, Preview, and production resources.
Skills
Check for `wrangler.jsonc/json/toml` and `cloudflare.config.ts`. New projects or cf-configured projects use Cloudflare’s `cf` CLI; do not add Wrangler. Inspect package manager, lockfile, scripts, and local Wrangler version; use local help/schema and relevant official docs. Before remote operations, confirm account/member, Worker, environment, and local/remote resource scope; review env inheritance, automatic provisioning, and secrets. `wrangler secret put/delete` creates a version and deploys immediately; use staged-version workflows where needed. Build/test or dry-run first; do not deploy, change routes, or write production data without authorization.
Permissions
Prerequisites
- Develop, troubleshoot, preview, configure resources, or deploy when Wrangler config exists.
Permissions
- May change remote resources, secrets, or deployed versions; confirm account, environment, and permission.
Limitations
Use only with Wrangler config and no cloudflare.config.ts; prefer local version/schema. Production secret put/delete deploys immediately.
Pinned upstream source
- Repository
- cloudflare/skills
- File path
- skills/wrangler/SKILL.md
- Pinned commit
53395984c3ea1925d00fce03b266112302f050e6- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: Apache-2.0
Compatible tools
project-local Wrangler CLI · Wrangler config schema · Workers docs
Main topic
Take a coding Agent change from context to verification