Skip to content
Back to skills

Wrangler

ASecurity

Use before running Wrangler deploy, dev, tail, or types for Cloudflare Workers. Account resources (D1, KV, R2, DNS, secrets) use the cf CLI.

  • 44 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 5, 2026
developmentnode

Works with

  • cli

Security analysis

A100/100

Scanned September 30, 2026

npx -y skills add Charles5277/nuxt-supabase-starter --skill wrangler --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Wrangler?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Wrangler
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/charles5277-wrangler/badge)](https://www.skillsdirectory.com/skills/charles5277-wrangler)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: wrangler
description: "Use before running Wrangler deploy, dev, tail, or types for Cloudflare Workers. Account resources (D1, KV, R2, DNS, secrets) use the cf CLI."
---

<!-- clade-skill-scope: project -->

# Wrangler CLI

Your knowledge of Wrangler CLI flags, config fields, and subcommands may be outdated. Prefer retrieval over pre-training for Wrangler tasks.

## Retrieval Sources

Fetch the latest information before writing or reviewing Wrangler commands and config.

- Wrangler docs: `https://developers.cloudflare.com/workers/wrangler/`
- Cloudflare Workers docs: `https://developers.cloudflare.com/workers/`
- Local schema: `node_modules/wrangler/config-schema.json`

## First Step

Use the project's package manager and locally installed Wrangler. Check `package.json`, the lockfile, and the deployment scripts, then query that binary's version and help (for a pnpm project: `pnpm exec wrangler --version`). If the declared dependency is not installed, restore the project dependencies. If no dependency is declared, select a compatible version through the project's dependency workflow before installing it.

## Key Guidelines

- Prefer `wrangler.jsonc` over TOML for newer configuration support.
- Keep the project’s tested `compatibility_date`; validate affected runtime behavior when changing it.
- Run `wrangler types` after config changes.
- Run the project’s typecheck/tests and `wrangler deploy --dry-run` with the intended config and environment before deploy. The [deploy dry run](https://developers.cloudflare.com/workers/wrangler/commands/workers/#deploy) compiles without deploying; live bindings and production behavior still need their own verification.
- Use environments for staging and production.

## 帳號資源操作走 `cf` CLI

D1 / KV / R2 / Vectorize / Queues / DNS / Worker secret 等帳號資源的查詢與異動 **MUST** 走 `cf-cli` skill,**NEVER** 用 `wrangler d1|kv|r2|secret|...` 子指令改打遠端。wrangler 只留給 deploy、`wrangler dev`、`wrangler tail`、`wrangler types`、config 驗證、查 dev server 的本機資料(`--local`),以及 CI workflow 內的步驟(D1 migration、`pre-migration-bookmark.sh` 等;邊界見 `cloudflare-workers.md` § 8)。

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.