# Cloudflare Deploy

> Deploy applications and supporting infrastructure to Cloudflare using Workers, Pages, and related platform services.

- Skill: `michaelschecht/cloudflare-deploy` (Agent Skill)
- Install (CLI): `npx skillmds@latest add michaelschecht/cloudflare-deploy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/michaelschecht/cloudflare-deploy/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: michaelschecht (https://skillmd.com/u/michaelschecht)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/michaelschecht/cloudflare-deploy

---


# cloudflare-deploy

Deploy applications and supporting infrastructure to Cloudflare using Workers, Pages, and related platform services.

## Overview

Use this skill when:

- The user wants to deploy or host on Cloudflare
- A project targets Workers, Pages, KV, R2, D1, or Durable Objects
- You need to set up environment bindings or edge-friendly deployment config
- You are migrating a small app or API to Cloudflare's edge runtime

## Workflow

1. Identify the runtime target: Workers, Pages, or a hybrid setup.
2. Confirm the build output, entrypoint, and required bindings.
3. Configure environment variables, secrets, and resource bindings explicitly.
4. Validate local build output before deployment.
5. Deploy to preview or staging first when possible.
6. Verify routes, logs, and edge-runtime compatibility after release.

## Deployment Checklist

- Entry file and runtime mode are correct
- Build command and output directory are explicit
- Secrets are stored as Cloudflare secrets, not plain config
- KV, D1, R2, Durable Objects, and queues are declared intentionally
- Custom domains and routes are mapped to the correct environment

## Common Concerns

### Workers

- Check runtime API compatibility
- Avoid unsupported Node assumptions unless compatibility mode is enabled
- Keep startup and dependency weight small

### Pages

- Confirm static build output path
- Separate framework build concerns from deployment config
- Verify edge functions only where needed

## Guardrails

- Do not assume a Node server can be deployed unchanged to Workers
- Avoid mixing production secrets into preview environments
- Verify database and storage bindings per environment
- Treat edge-runtime limitations as design constraints, not incidental bugs