Guide · Agent skill
How to use the Cloudflare Workers and DNS Deployer agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Cloudflare skill is a packaged set of instructions that teaches an AI agent how to deploy and manage Cloudflare Workers, Pages, KV, R2, D1, DNS and Queues, and how to build MCP servers as Workers. It is written for developers who already host projects on Cloudflare and want deploys run the same way each time, with checks after each change. After this guide you will know what the skill does, how to install it, how to phrase a request so it triggers, and what it needs before it will run.
Cloudflare Workers and DNS Deployerdanielmiessler/LifeOS · MIT Download the skill Quick start
- 1Download and unzip. Download the ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder.
- 2Or upload in the Claude apps. In the Claude apps, open Settings, then Capabilities, then Skills, and upload the ZIP.
- 3Add your Cloudflare credentials. Store the Cloudflare account ID and API token in ~/.claude/.env as Setup.md describes.
- 4Set up the deploy review. Configure a reviewer model from another vendor and any waivers, following Setup.md.
- 5Make a request. Ask in plain language, naming the worker or zone and the action, such as deploy or check logs.
- 6Check the report. Confirm the version ID, the live probe result and the resource identifier before accepting the change.
What the Cloudflare skill makes the agent do
An agent skill is a folder of instructions and helper files that an AI agent loads when a task matches its description. This skill covers Cloudflare work: deploying Workers, static sites, storage, DNS and queues with Cloudflare's cf command-line tool, and building MCP servers (tool servers that AI agents call) as Cloudflare Workers.
The skill routes every account-changing command through a LifeOS helper script, CfEnv.ts, which injects the Cloudflare API token into the cf process. For each deployment it asks for a live probe or version ID to confirm the change works, rather than assuming success. Read-only questions such as listing workers, versions, KV, DNS, D1 or logs are answered from live cf output.
- Deploys Workers, Pages, KV, R2, D1, DNS and Queues
- Converts Wrangler projects to the cf CLI
- Builds stateless MCP servers that meet its MCP spec reference
- Excludes non-Cloudflare deploys and MCP servers you only consume
Install the Cloudflare skill
Download the ZIP from this page and unzip it. For a personal setup, place the folder in ~/.claude/skills/. For a single project, place it in that project's .claude/skills/ folder. Alternatively, in the Claude apps, open Settings, then Capabilities, then Skills, and upload the ZIP there.
After installing, the skill's files should include SKILL.md, Setup.md, and the Intents and References folders. Setup.md covers the first-time configuration you need before any deploy.
- Personal: ~/.claude/skills/
- Project only: .claude/skills/ inside the project
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
Complete the one-time setup
Most steps depend on the LifeOS tooling. The skill needs a Cloudflare account and an API token stored in ~/.claude/.env, the cf CLI (beta, pinned to cf@1.0.0-beta.5 by CfEnv.ts), and the LifeOS TOOLS directory containing CfEnv.ts and Review.ts. Deploys also need a reviewer model from a different vendor, and the Node.js toolchain for the cf CLI and Vite plugin.
Work through Setup.md before your first deploy. It covers the two .env keys, the deploy review's reviewer and waivers, and the check that CfEnv's allowlist guard is in place.
- Cloudflare account and API token in ~/.claude/.env
- cf CLI (beta), pinned by CfEnv.ts
- LifeOS TOOLS directory with CfEnv.ts and Review.ts
- Reviewer model from another vendor for deploy review
- Node.js toolchain
Trigger the skill with natural requests
The skill loads when your request matches its trigger phrases. You do not need to name the skill. Plain requests such as deploying a worker, pushing a site to Cloudflare, or checking worker logs will route to the right intent. Name the resource and the action so the agent picks the correct file.
Requests to build an MCP server also trigger it, for example asking what shape an MCP server should take. Requests about MCP servers you only connect to as a client are outside the skill.
- "Deploy this worker to Cloudflare and tell me the version ID."
- "Create a D1 migration for the users table and apply it."
- "Show me the DNS records for example zone." (read-only)
- "Write an MCP server as a Cloudflare Worker that exposes our invoice tool."
Understand the safety gates and what runs
This skill runs scripts and uses the network. Deploy and DNS writes change real infrastructure, and a misapplied change can break a live site. Every non-dry-run deploy first runs the independent code review through Review.ts, and a blocker stops the deploy. After a deploy, the skill checks each declared domain's link card with a public fetch.
The skill also expects workers with a custom domain to turn off workers.dev and preview URLs, so the site answers only on its real address. Review the report for the version ID and the probe result before treating a change as done.
- Account writes run through CfEnv.ts, not raw cf or wrangler
- Deploy review blocks a deploy on a blocker and fails closed without a reviewer
- Live changes need a review step; do not bypass it for production
- Check the version ID and probe output in every report
Tips for reliable results
Ask for the verification explicitly, for example a probe of the live URL. Keep the Cloudflare token scoped to the account you intend to change. If a deploy fails with an authentication error, ask the agent to check the identity and the scope before changing the token, because the skill is written to diagnose auth this way.
Do not assume a pinned version changes on its own. The pin in CfEnv.ts controls which cf version runs, and changing it is a deliberate step that requires checking each command your tooling uses.
- Name the worker, zone and environment in each request
- Ask for the version ID and a live probe in the report
- Diagnose auth failures before rotating tokens
- Treat the pinned cf version as a deliberate change
What people use it for
- Deploy a Worker to its custom domain with workers.dev and preview URLs turned off
- Apply a D1 migration and confirm the schema with a SELECT query
- Read live DNS records or worker versions without changing anything
- Convert a Wrangler project to the cf CLI and redeploy it
- Build a stateless MCP server as a Cloudflare Worker following the skill's spec
Frequently asked questions
How do I install the Cloudflare agent skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. You can also upload the ZIP in the Claude apps under Settings, then Capabilities, then Skills.
What do I need before the Cloudflare skill works?
You need a Cloudflare account and API token in ~/.claude/.env, the cf CLI beta that CfEnv.ts pins, the LifeOS TOOLS directory with CfEnv.ts and Review.ts, a reviewer model from another vendor, and the Node.js toolchain. Setup.md walks through the configuration.
Is the Cloudflare skill free?
The source lists the skill's licence as MIT. It does not state pricing for Cloudflare itself, so check your own Cloudflare account terms for any costs.
Can I use this skill without LifeOS?
Not as described here. Most steps depend on the LifeOS CfEnv.ts helper and its .env setup, so users without that tooling are not the intended audience.
Does the skill deploy to hosts other than Cloudflare?
No. The skill explicitly excludes non-Cloudflare deploys. It also excludes MCP servers you only consume rather than build.
What should I do if a deploy fails with an authentication error?
Ask the agent to trace the failure through the auth identity check and a probe that matches the token's scope before rotating anything. The skill is written to avoid false conclusions that a token is dead.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you already host projects on Cloudflare and want deploys, DNS changes and queries run through one tool with verification and a review gate. Pick something else if you lack a Cloudflare account or the LifeOS CfEnv.ts tooling, or if you deploy to other hosts.
Download the skill