Cloudflare Wrangler

Reviewed 2026-10-23devopsPrompt / Rule# cloudflare # wrangler # workers # deploy # serverless

Cloudflare's official wrangler skill: tells an AI agent how to deploy, configure and debug existing Wrangler-based Workers projects using current Cloudflare docs.

Security Reviewed

Instruction-only skill from Cloudflare; it acts on your Cloudflare account through Wrangler and fetches current docs, with explicit rules for secrets and token scope.

Install Cloudflare Wrangler in Google Antigravity

Antigravity loads skills from .agents/skills/ in your project or ~/.gemini/config/skills/ for all projects (official docs). Full guide

EasiestOption 1: paste this to your Antigravity agent

Install the "Cloudflare Wrangler" skill for Google Antigravity.
Follow the steps at https://www.antigravityskills.org/install/cloudflare-wrangler.md (source: https://github.com/cloudflare/skills/tree/main/skills/wrangler).
Before running anything, show me what you will download and whether it includes scripts, and wait for my OK.
Install it into this project (.agents/skills/) unless I say global. When done, check that Antigravity lists it as an installed skill.

The agent reads the install file, shows you what it will download and waits for your OK.

Option 2: install it yourself

1. Download the repository
```
git clone --depth 1 https://github.com/cloudflare/skills /tmp/cloudflare-skills
```
README, Clone / Copy. The repository holds 19 skills; copy only the ones you need.
2. Copy into this workspace (project skill)
```
mkdir -p .agents/skills && cp -r /tmp/cloudflare-skills/skills/wrangler .agents/skills/
```
Run from your project root. Antigravity reads workspace skills from <project>/.agents/skills/<folder>/. Also copy skills/cf-cli if you want the hand-over for new projects to work.
3. Or install globally (all projects)
```
mkdir -p ~/.gemini/config/skills && cp -r /tmp/cloudflare-skills/skills/wrangler ~/.gemini/config/skills/
```
Use this instead of the previous step to have the skill in every workspace. Global skills folder from Antigravity's docs (antigravity.google/docs/skills).
4. Or use the skills CLI
```
npx skills add https://github.com/cloudflare/skills --skill wrangler -a antigravity
```
The Cloudflare README documents npx skills add; --skill and -a antigravity come from the vercel-labs/skills README, which installs to .agents/skills/ (with -g: ~/.gemini/antigravity/skills/). Use -a antigravity-cli for the Antigravity CLI.
5. Check that Antigravity sees it
Antigravity 2.0 app: start a new conversation and ask "What skills do you have?" (the app has no /skills command; typing / and the skill name also finds it, sometimes only after your first message). Antigravity CLI: run /skills; in a session that was already open, run /skills reload first. wrangler should be listed.

The cloudflare/skills README does not mention Antigravity (it covers Claude Code, VS Code / GitHub Copilot, Cursor, npx skills and a clone-and-copy table, among other hosts). The skill also needs Wrangler in your project and a Cloudflare login.

Using Claude Code, Cursor or Codex? See other assistants below.

What is Cloudflare Wrangler?

wrangler is the Wrangler CLI skill from Cloudflare's official cloudflare/skills repository. It tells an AI agent how to run, configure and troubleshoot Wrangler in an existing Workers project (deploys, bindings, secrets, environments, Workers Previews and rollbacks) by checking the project's own Wrangler version and fetching the current Cloudflare docs page first, instead of relying on memorized flags. It is for developers whose project already has a wrangler.jsonc, wrangler.json or wrangler.toml. What we counted at commit 86505e4 (2026-10-15, HEAD on 2026-10-23; the wrangler folder is unchanged since cf56dd4 on 2026-10-12): one SKILL.md, 71 lines and 11,626 bytes, no scripts; it links 30 distinct developers.cloudflare.com pages, and a table maps 15 tasks to the page to read. It is one of 19 skills in the repository. Since commit cf56dd4 (2026-10-12) the skill no longer covers new projects: for those, or projects with cloudflare.config.ts, it hands over to the cf-cli skill added the same day and says not to add Wrangler.

How to use Cloudflare Wrangler?

Install the skill, open a project that already uses Wrangler, and ask for the change in plain words. The agent first finds the package manager, the installed Wrangler version, the scripts and the config file, and runs Wrangler through the project's own scripts. It then fetches the matching Cloudflare docs page (or uses the Cloudflare MCP docs tool if you have it), makes the change, regenerates types with wrangler types and checks with wrangler deploy --dry-run where supported, and reports what changed, the target environment and any checks it could not do. Log in with wrangler login, or use an account API token for narrower permissions.

Key features of Cloudflare Wrangler

✓Inspects package manager, Wrangler version, scripts and config before running anything; does not silently upgrade Wrangler
✓Task-to-docs table with 15 rows (commands, config and bindings, framework deploys, migrations, environments, secrets, types, local dev, permissions, Previews, auth, claim deployments)
✓Prefers wrangler.jsonc for new config and sets a new project's compatibility date to today
✓Workers Previews guidance (needs project-local Wrangler 4.135.0 or later) and a reminder that Preview URLs are public unless protected
✓Secret rules: keep values out of arguments, code and logs; wrangler secret put and secret delete deploy immediately
✓Validation with wrangler types and wrangler deploy --dry-run, plus a report of unresolved gaps

When to use Cloudflare Wrangler

1Deploying an existing Worker or framework app
2Adding a KV, R2, D1 or other binding to wrangler config
3Setting up staging and production environments
4Creating branch or pull-request Preview environments
5Fixing Wrangler login or account selection problems

Installation & Setup Guide

Agent Rules / Prompt Setup

Follow these steps (taken from the project's own docs) to configure Cloudflare Wrangler in your development environment.

Step 1: Claude Code: pluginClaude Code

/plugin marketplace add cloudflare/skills
/plugin install cloudflare@cloudflare

README, Claude Code. Installs all Cloudflare skills plus the remote Cloudflare MCP server (mcp.json).

Step 2: Claude Code: copy only this skillClaude Code

git clone --depth 1 https://github.com/cloudflare/skills /tmp/cloudflare-skills && mkdir -p ~/.claude/skills && cp -r /tmp/cloudflare-skills/skills/wrangler ~/.claude/skills/

README, Clone / Copy table: Claude Code reads ~/.claude/skills/.

Step 3: CursorCursor

mkdir -p ~/.cursor/skills && cp -r /tmp/cloudflare-skills/skills/wrangler ~/.cursor/skills/

README: install from the Cursor Marketplace, add via Settings > Rules > Add Rule > Remote Rule (Github) with cloudflare/skills, or copy into ~/.cursor/skills/ (Clone / Copy table).

Usage Example & Verification

Prompt / Request Example

1) Our example: "Add a D1 binding called DB to my Worker and deploy it to staging."
-> What happens: the agent reads package.json, the lockfile and wrangler.jsonc, fetches the configuration reference, checks whether the staging environment needs its own binding (SKILL.md: some fields must be set per environment), edits the config, runs wrangler types and wrangler deploy --dry-run --env staging, then deploys and reports the environment it touched.

2) Our example: "Set the API_TOKEN secret on production."
-> What happens: it uses the interactive wrangler secret put input so the value never appears in a command line or log, and warns that this creates and deploys a new version at once; for a staged change it points to the wrangler versions secret workflow.

3) Our example: "Create a Preview for this branch."
-> What happens: it checks that the project pins Wrangler 4.135.0 or later, reads the Previews configuration and resource pages, asks which Worker or environment you mean, and tells you the Preview URL is public unless you add access controls.

Installation Confirmation Method

In Antigravity: Antigravity 2.0 app: start a new conversation and ask "What skills do you have?" (the app has no /skills command; typing / and the skill name also finds it, sometimes only after your first message). Antigravity CLI: run /skills; in a session that was already open, run /skills reload first. wrangler should be listed. Then, in a project with a wrangler.jsonc, ask "which Wrangler version and config does this project use?"; the agent should read package.json and the config before running anything.

Security Review

Static review

Reviewed Date

2026-10-23

Audited Ref / Commit

86505e44f87d801aa1864a3c4109e9a8ae5c409f

Reviewer

antigravityskills.org (static code review)

Instruction-only skill from Cloudflare; it acts on your Cloudflare account through Wrangler and fetches current docs, with explicit rules for secrets and token scope.

Full review: scope, findings, risks

Audit Scope:Static review of cloudflare/skills at commit 86505e4 (2026-10-15, HEAD on 2026-10-23): skills/wrangler/SKILL.md, README.md, mcp.json, plugin.json, the skills/ listing and LICENSE, plus the diff from our earlier reviewed commit 5339598 (README.md and the skills listing changed; skills/wrangler/SKILL.md did not) and from 41e0d19 (skills/wrangler/SKILL.md changed in cf56dd4). Wrangler itself was not reviewed.

Key Findings:Instruction-only skill: one SKILL.md, no scripts. The agent runs the project's Wrangler (deploy, secret put/delete, types, rollback) and fetches developers.cloudflare.com pages. Auth via wrangler login or an account API token. Plugin installs add the remote Cloudflare MCP server (https://mcp.cloudflare.com/mcp); a folder copy does not.

Identified Operational Risks & Permissions:Can deploy to production and change secrets; secret put/delete deploy immediately; a local Worker can still reach real remote resources; Wrangler can overwrite dashboard variables and routes; Preview URLs are public unless protected (SKILL.md warns about all of these). Static review only.

Static review at commit 86505e4. skills/wrangler/SKILL.md is the only file in the folder and contains no scripts. It tells the agent to run Wrangler through the project's package manager, fetch docs from developers.cloudflare.com (30 distinct pages linked) or use the Cloudflare MCP docs tool, and validate with wrangler types and wrangler deploy --dry-run. It warns that wrangler secret put and secret delete deploy immediately, that a local Worker can still access real remote resources, that Wrangler can overwrite dashboard variables and routes, that omitted resource identifiers can trigger automatic provisioning, that rollbacks do not roll back data, and that Preview URLs are public unless access controls are set. Before remote commands it must identify the authenticated member or token and its scope, prefer the narrowest scope, and never ask the user to paste a token into chat. The repository's mcp.json, used only by plugin installs, adds https://mcp.cloudflare.com/mcp.

Operational Notes & Known Limitations

Known Limitations

•Only for projects that already have wrangler.jsonc, wrangler.json or wrangler.toml; for new projects or cloudflare.config.ts it defers to the cf CLI (cf-cli skill), since commit cf56dd4
•Needs Wrangler in the project and a Cloudflare login (wrangler login) or an account API token; wrangler login does not support granular permissions (SKILL.md)
•Relies on fetching developers.cloudflare.com pages or the Cloudflare MCP docs tool; offline it must say what it could not check
•Workers Previews need project-local Wrangler 4.135.0 or later; a newer global install does not count
•A dry run checks build and packaging only, not remote resources or runtime behaviour (SKILL.md)
•The README install options (plugin, npx skills) add all 19 Cloudflare skills unless you pick one; the plugin also adds the remote MCP server

Frequently Asked Questions

Is the Cloudflare Wrangler skill safe?

The skill is one SKILL.md with no scripts (static review of commit 86505e4). It acts on your Cloudflare account through Wrangler, so it can deploy, change secrets and roll back. It tells the agent to confirm the account and target first, use the narrowest token scope, and never ask you to paste a token into chat.

How do I install the wrangler skill in Antigravity?

Clone cloudflare/skills and copy skills/wrangler to .agents/skills/ (or ~/.gemini/config/skills/), or run npx skills add https://github.com/cloudflare/skills --skill wrangler -a antigravity. Then ask "What skills do you have?" (Antigravity CLI: /skills).

Should I use the wrangler skill or cf-cli?

Since 2026-10-12 the wrangler skill says: use it only when the project already has a Wrangler config and no cloudflare.config.ts; for new projects use the cf CLI and the cf-cli skill.

Does it need the Cloudflare MCP server?

No. It uses the MCP docs tool if available and otherwise fetches developers.cloudflare.com pages directly. The Claude Code plugin adds the remote server https://mcp.cloudflare.com/mcp (mcp.json); a folder copy does not.

Supported Platforms

antigravityclaudecursor

View Source on GitHub

Keep exploring this topic

Browse the full Antigravity skills directory for more source-linked skills with install steps and static safety reviews.

More devops skills #cloudflare #wrangler #workers #deploy Use cases

Related Skills

🚀

Vercel Specialist

@sickn33

Community skill with patterns and a list of known pitfalls for deploying Next.js apps to Vercel: environment variables, edge vs serverless, previews, domains and caching.

Static reviewinstructions onlyoffline

vercelnextjs

🛡️