Agent skill · vasilyu1983
software-cloudflare-wrangler
Guides Cloudflare Wrangler CLI usage for Workers, bindings, deploys, local dev, and config. Use when running or reviewing wrangler commands.
What it needs
About 5k tokens when loaded.
What this skill does
Wrangler CLI Your knowledge of Wrangler CLI flags, config fields, and subcommands may be outdated. Prefer retrieval over pre-training for any Wrangler task. Quick Reference Task Read or Run Outcome ------ ------------- --------- Check install/version and core commands references/getting-started.md Current Wrangler source, install, and command basics Edit config or bindings references/configuration.md wrangler.jsonc shape and generated types Run locally or deploy safely references/local-development-and-deployment.md Dev modes, remote bindings, dry runs, secrets, rollbacks Manage storage/data resources references/storage-and-data.md KV, R2, and D1 commands/config Manage Cloudflare platform services references/platform-services.md Vectorize, Hyperdrive, Workers AI, Queues, Containers, Workflows, Pipelines, Secrets Store Debug, observe, test, or deploy Pages references/pages-observability-testing.md Pages, logs, tests, troubleshooting, best practices Workflow 1. Check the installed Wrangler version or project dependency before writing commands. 2. Retrieve current Cloudflare docs or the local nodemodules/wrangler/config-schema.json for flags, config fields, and binding shapes. 3. Choose the smallest relevant reference below and verify syntax against docs/schema before running commands. 4. Prefer wrangler.jsonc, generate types after binding/config edits, and validate with local dev, dry-run deploy, or the safest available project check. 5. Surface any command that can mutate production resources before running it. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vasilyu1983/software-cloudflare-wrangler