How do I install the Cloudflare skill?

Run npx skillmds@latest add sheshiyer/cloudflare 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 safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cloudflare?

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 free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cloudflare?

Sheshiyer (@sheshiyer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cloudflare by sheshiyer — Agent Skill

Name: Cloudflare
Author: Sheshiyer

Cloudflare

Deploy and manage Cloudflare Workers, MCP servers, and Pages, with auth-token gotchas baked in. USE WHEN deploying a Worker or MCP server, publishing a Pages site, or debugging a Cloudflare deploy/auth failure.

Sheshiyer bb41db3 3 files · 20.2 KB Updated Sep 17, 2026

File contents

Cloudflare Skill

Deploy and manage Cloudflare Workers, MCP servers, and Pages.

Workflow Routing

Create MCP server or Worker → Workflows/Create.md
Troubleshoot deployment issues → Workflows/Troubleshoot.md

Quick Reference

Account ID: Set via CF_ACCOUNT_ID environment variable
Worker URL format: https://[worker-name].[your-subdomain].workers.dev

Deployment Commands

Workers Deployment

# Unset tokens that interfere with wrangler login-based auth
(unset CF_API_TOKEN && unset CLOUDFLARE_API_TOKEN && wrangler deploy)

Pages Deployment

🚨 CRITICAL: ALL env tokens lack Pages permissions. MUST unset them to use OAuth:

# ALWAYS unset tokens for Pages - OAuth login works, tokens don't
(unset CF_API_TOKEN && unset CLOUDFLARE_API_TOKEN && npx wrangler pages deploy dist --project-name=PROJECT_NAME --commit-dirty=true)

Known Pages Projects:

Project	Directory	Deploy Command
[project]	`~/Projects/[project]`	`(unset CF_API_TOKEN && unset CLOUDFLARE_API_TOKEN && npx wrangler pages deploy dist --project-name=[project] --commit-dirty=true)`

Critical Notes

Workers: Unset CF_API_TOKEN and CLOUDFLARE_API_TOKEN before deploying - they interfere with wrangler login-based auth
Pages: 🚨 UNSET ALL TOKENS - None of the API tokens have Pages permissions. OAuth-based wrangler login is the ONLY method that works.

Examples

Example 1: Deploy a Worker

User: "deploy the MCP server to Cloudflare"
→ Invokes CREATE workflow
→ Unsets env tokens, runs wrangler deploy
→ "Deployed to https://mcp-server.[subdomain].workers.dev"

Example 2: Deploy Pages site

User: "deploy daemon to Cloudflare"
→ Builds dist/, unsets tokens
→ Runs wrangler pages deploy
→ "Deployed daemon to Cloudflare Pages"

Example 3: Fix deployment error

User: "Cloudflare deploy is failing with auth error"
→ Invokes TROUBLESHOOT workflow
→ Identifies token interference
→ "Fixed - tokens were overriding OAuth. Redeployed successfully."

---name: cloudflaredescription: Deploy and manage Cloudflare Workers, MCP servers, and Pages, with auth-token gotchas baked in. USE WHEN deploying a Worker or MCP server, publishing a Pages site, or debugging a Cloudflare deploy/auth failure.---# Cloudflare SkillDeploy and manage Cloudflare Workers, MCP servers, and Pages.## Workflow Routing - **Create** MCP server or Worker → `Workflows/Create.md` - **Troubleshoot** deployment issues → `Workflows/Troubleshoot.md`## Quick Reference- **Account ID:** Set via `CF_ACCOUNT_ID` environment variable- **Worker URL format:** `https://[worker-name].[your-subdomain].workers.dev`## Deployment Commands### Workers Deployment```bash# Unset tokens that interfere with wrangler login-based auth(unset CF_API_TOKEN && unset CLOUDFLARE_API_TOKEN && wrangler deploy)```### Pages Deployment**🚨 CRITICAL: ALL env tokens lack Pages permissions. MUST unset them to use OAuth:**```bash# ALWAYS unset tokens for Pages - OAuth login works, tokens don't(unset CF_API_TOKEN && unset CLOUDFLARE_API_TOKEN && npx wrangler pages deploy dist --project-name=PROJECT_NAME --commit-dirty=true)```**Known Pages Projects:**| Project | Directory | Deploy Command ||---------|-----------|----------------|| [project] | `~/Projects/[project]` | `(unset CF_API_TOKEN && unset CLOUDFLARE_API_TOKEN && npx wrangler pages deploy dist --project-name=[project] --commit-dirty=true)` |## Critical Notes- **Workers:** Unset `CF_API_TOKEN` and `CLOUDFLARE_API_TOKEN` before deploying - they interfere with wrangler login-based auth- **Pages:** 🚨 **UNSET ALL TOKENS** - None of the API tokens have Pages permissions. OAuth-based wrangler login is the ONLY method that works.## Examples**Example 1: Deploy a Worker**```User: "deploy the MCP server to Cloudflare"→ Invokes CREATE workflow→ Unsets env tokens, runs wrangler deploy→ "Deployed to https://mcp-server.[subdomain].workers.dev"```**Example 2: Deploy Pages site**```User: "deploy daemon to Cloudflare"→ Builds dist/, unsets tokens→ Runs wrangler pages deploy→ "Deployed daemon to Cloudflare Pages"```**Example 3: Fix deployment error**```User: "Cloudflare deploy is failing with auth error"→ Invokes TROUBLESHOOT workflow→ Identifies token interference→ "Fixed - tokens were overriding OAuth. Redeployed successfully."```

Frequently asked questions