How do I install the Cloudflare Worker Deploy skill?

Run npx skillmds@latest add yolo-labs-hq/cloudflare-worker-deploy in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cloudflare Worker Deploy safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cloudflare Worker Deploy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cloudflare Worker Deploy free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Cloudflare Worker Deploy?

yolo-labs-hq (@yolo-labs-hq) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cloudflare Worker Deploy by yolo-labs-hq

Name: Cloudflare Worker Deploy
Rating: 4.2 (5 reviews)
Author: yolo-labs-hq

Cloudflare Worker Deploy

Deploy a Cloudflare Worker via wrangler with env-aware secrets. Pick the right wrangler.jsonc env, run wrangler deploy, and verify the deploy with wrangler tail. Covers common errors — missing secret bindings, KV namespace mismatches, route collisions.

yolo-labs-hq Updated Sep 22, 2026

File contents

Cloudflare Worker deploy

Pre-flight

Confirm wrangler.jsonc exists at the repo root. Modern Cloudflare projects use wrangler.jsonc (JSON with comments), not wrangler.toml. If you see only wrangler.toml, ask before migrating.
List the configured environments — they're under the env.* keys in the JSONC.
Verify any secrets required by the env are set: wrangler secret list --env <env>.

Deploy

wrangler deploy --config wrangler.jsonc --env <env>

Watch the output for the deployed route. If you see "binding not found" the secret/KV/D1 binding referenced in JSONC is missing in this environment — set it before re-running.

Verify

wrangler tail --env <env>

Send a request to the route. If logs don't appear, the route or zone is misconfigured. Don't rely on curl against the workers.dev subdomain to verify production routes — they're separate from custom-domain routes.

OpenNext / Next.js sites

If wrangler.opennext.jsonc is also present, the deploy command for that surface is:

wrangler deploy --config wrangler.opennext.jsonc --env <env>

Never deploy as Cloudflare Pages — modern Cloudflare Next.js deploys go through OpenNext workers, not Pages.

Rollback

wrangler rollback reverts to the previous deployment. It does not roll back secrets or KV/D1 schema — those are out-of-band and need their own rollback plan.

Frequently asked questions