Agent skill · software engineering · steipete
wrangler
Wrangler CLI: Workers, KV, tail, deploy, account routing.
Why this skill is useful
Adds specific commands and best practices for using the Wrangler CLI with Cloudflare services that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. Requires cloudflare account access. About 1k tokens when loaded. Last updated 2026-08-06. 6,510 stars on the source repository.
What this skill does
Wrangler Use for Cloudflare Wrangler CLI work: deploys, tails, KV/R2/D1/Queues/Workers, secrets, bindings, and account routing. Defaults Retrieval first for flags/config: wrangler --help, subcommand --help, local nodemodules/wrangler/config-schema.json, then Cloudflare docs. Prefer repo wrapper: npm exec --yes --package wrangler -- wrangler ... unless repo has its own script. wrangler whoami before account-sensitive work. ReleaseBar prod account: Steipete@gmail.com's Account / de09342a728de2c25c85cc6b34d68739. OpenClaw projects: use OpenClaw account / 91b59577e757131d68d55a471fe32aca. Ask if unsure. Pitfalls Do not invent flags from memory. Wrangler 4 removed/changed some old flags; confirm with --help. wrangler kv key list has no --limit; use --prefix and filter locally. Run Wrangler KV/list/get/admin reads serially when workerd/local storage starts up; parallel runs can hit SQLite SQLITEBUSY. wrangler tail --sampling-rate must be >0 and <1; use 0.999 for near-full sampling, not 1. Stop tails you start. Use a PTY when interactive stop matters; otherwise kill the exact wrangler tail <worker> process. Never print secrets. Query exact secret names only; do not dump env. Quick Commands Account Check For repo config, read wrangler.toml / wrangler.json(c) before commands. If config account and intended product disagree, stop and ask.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/wrangler