Index of every page on this site: llms.txt
All skills
cloudflare avatar

/wrangler

@5108325 official
by cloudflarecloudflare/skills3.4k stars
357
Run it yourself

Run or troubleshoot Wrangler CLI commands in projects that have a wrangler.jsonc, wrangler.json, or wrangler.toml file, including local development, Previews, deployment, and resource management. For new projects and projects without a Wrangler configuration file, use the cf CLI instead.

Use this Skill: https://skilld.dev/gh/cloudflare/skills/wrangler

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesskill-feedback.md

≈696 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Skill feedback

GitHub issues are public: anyone can read an issue once it is posted. Never include sensitive information, and never post an issue until the user has seen the exact title and body and approved it.

Use this when the user reports that the wrangler skill gave incorrect or outdated guidance, is missing information, or could be improved. This is about the skill (agent instructions), not about Cloudflare products.

What not to include

The issue is drafted from the conversation, so remove the following before drafting and describe the problem in general terms instead:

  • Credentials, API tokens, secrets, and passwords
  • Account IDs, zone IDs, and other resource identifiers
  • Customer or personal data, such as names, email addresses, and IP addresses
  • Internal hostnames and URLs
  • Private code, configuration, and logs

Steps

  1. Ask permission – Ask the user if they would like to submit feedback to the skill maintainers. If they decline, move on.

  2. Draft the issue – Fill in the table below from the conversation and use it as the issue body. Always identify which specific file and section caused the problem. Leave out everything listed in What not to include.

  3. Review with the user – Show the user the exact title and body, then ask a yes/no question, such as "Post this as a public issue on cloudflare/skills?" Submit only after the user answers yes. If they ask for changes, apply them and ask again. If they answer no, do not post. Agreeing to send feedback in step 1 is not approval of the text.

  4. Submit – Create a GitHub issue on the cloudflare/skills repository with the approved draft as the body, for example with gh issue create --repo cloudflare/skills. The title must follow this format: skill-feedback: wrangler: <summary of the problem>.

  5. Share the result – Share the issue URL with the user after submission. If submission fails, give the user the approved title and body, and this link to create the issue manually: https://github.com/cloudflare/skills/issues/new

Issue body

Field Value
Type bug (incorrect guidance), outdated, missing, or improvement
Skill wrangler
Source File and section, e.g. SKILL.md > "Section name" or references/<file>.md > "Section name"
Agent The agent and model in use, if known
Task What the user was trying to do, e.g. "deploy a preview"
Expected What should have happened, e.g. "Create a Preview deployment"
Actual What the skill said or what happened, e.g. "Unknown option: --preview"
Impact The effect on the user, e.g. "Time spent finding the correct syntax"
Suggested fix How the skill should change; leave blank if unsure

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning23d5 checks · Risk SAFE
  • Gen Agent Trust Hub23d

    This skill provides guidance for using the Wrangler CLI within Cloudflare Worker projects. It incorporates security best practices, such as protecting secrets and using project-local dependencies. No security risks were identified.

  • Socket23d

    No alerts

  • Snyk23d

    Risk: LOW · No issues

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    1 finding · Score: 82/100

Signed by skilld at 5108325. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated 4 weeks ago
  • CLI
  • cloudflare
  • workers
  • wrangler
  • deployment
  • kv
  • r2
  • d1
  • vectorize
  • hyperdrive

README badge

README badge for cloudflare/skills/wrangler

Installs Cloudflare Workers CLI (Wrangler) and provides up-to-date command syntax, config schema, and binding references for deploying and managing Workers across KV, R2, D1, Vectorize, Hyperdrive, AI, and other Cloudflare services. Prioritizes live documentation retrieval over pre-trained knowledge to avoid stale CLI flags and config fields.

Generated from the current SKILL.md.

Does this skill work with Wrangler v3?
No. This skill requires Wrangler v4.x or later. Check your version with `wrangler --version` and upgrade with `npm install -D wrangler@latest` if needed.
Should I use wrangler.jsonc or wrangler.toml?
Prefer wrangler.jsonc (JSON config). Newer Cloudflare Workers features are JSON-only, and TOML support is being phased out.
Does local dev use real Cloudflare resources by default?
No. By default, `wrangler dev` simulates bindings locally (KV, R2, D1, etc.). Set `remote: true` on specific bindings to connect to live resources, which is required for Workers AI.
How do I handle secrets securely?
Use `wrangler secret put API_KEY` for interactive prompts, or pipe from a file: `wrangler secret put PRIVATE_KEY < path/to/key.pem`. Never pass secrets as command arguments or log them.
What should I do after changing wrangler.jsonc?
Run `wrangler types` to regenerate TypeScript bindings and ensure your bindings are correctly typed.

Generated from the current SKILL.md. These answers refresh after source changes.