10 skills · 6 categories

Claude Code skills for Cloudflare

Cloudflare skills for Workers, Durable Objects, R2, edge caching and bot defense, plus the frameworks that deploy to the edge. Useful when latency, egress cost or abuse is the problem to solve.

Start with these

  1. 1

    Cloudflare Workers

    Right storage per binding, typed env, one-command rollback

    Claude configures Workers with explicit compatibility dates, generated binding types and per-environment bindings, then picks KV, D1, R2, Durable Objects or Queues from the access pattern rather than habit. Code stays inside CPU and memory limits, tests run in the real Workers runtime via Vitest, and releases go out as versions with traffic splitting and a known rollback.

  2. 2

    Hono on the Edge

    One typed API for Workers, Bun, Deno and Node

    Claude writes Hono apps against Web standard APIs so they run on Workers, Bun, Deno or Node, with Bindings and Variables typed from the start. Inputs pass through Zod or Standard Schema validators, errors flow through one onError handler, and routes are chained so the exported AppType gives the frontend a fully typed hc client without hand-written fetch wrappers.

  3. 3

    S3 and R2 Object Storage

    Private buckets, presigned uploads, no surprise bills

    Claude keeps buckets private with Block Public Access and ACLs disabled, then serves files through short-lived presigned URLs or CloudFront with origin access control. Uploads go straight from the browser with server-chosen keys and enforced size limits, large files use multipart with exposed ETags, and lifecycle rules abort stale uploads and expire old versions on S3 or R2.

All 10 Cloudflare skills

Grouped by category. Each card opens the full playbook, example prompts and install commands.

Cloud Platforms 5

No. 182

Cloudflare Workers

Right storage per binding, typed env, one-command rollback

Claude configures Workers with explicit compatibility dates, generated binding types and per-environment bindings, then picks KV, D1, R2, Durable Objects or Queues from the access pattern rather than habit. Code stays inside CPU and memory limits, tests run in the real Workers runtime via Vitest, and releases go out as versions with traffic splitting and a known rollback.

cloudflare-workers 203 lines
No. 188

S3 and R2 Object Storage

Private buckets, presigned uploads, no surprise bills

Claude keeps buckets private with Block Public Access and ACLs disabled, then serves files through short-lived presigned URLs or CloudFront with origin access control. Uploads go straight from the browser with server-chosen keys and enforced size limits, large files use multipart with exposed ETags, and lifecycle rules abort stale uploads and expire old versions on S3 or R2.

s3-object-storage 183 lines
No. 189

Supabase Backend

Treat the database as the security boundary it is

Claude builds Supabase projects with the CLI and versioned migrations, enables RLS on every exposed table with per-operation policies that are indexed and tested as two different users, and keeps the secret key off clients. Server auth uses @supabase/ssr with verified users, storage paths are scoped by user folder, and types are regenerated after each schema change.

supabase-backend 204 lines
No. 186

Netlify Deploys

Builds, redirects and functions that behave per context

Claude moves Netlify configuration into netlify.toml with pinned Node versions, monorepo base directories and ignore commands, then scopes environment variables per deploy context. Redirects are ordered with shadowing and force understood, assets get immutable caching, functions and forms follow current limits, and every change is checked on a deploy preview with a one-step rollback ready.

netlify-deploys 265 lines
No. 190

Vercel Deploys

Reproducible builds, scoped env vars, instant rollback

Claude reproduces Vercel builds locally with vercel pull and vercel build before guessing, scopes env vars per Production, Preview and branch, and remembers that changes need a redeploy. Functions run on the Node.js runtime near the database with sensible maxDuration, previews stay protected, monorepo builds skip unaffected apps, and production moves by promotion with a known rollback.

vercel-deploys 158 lines

Install

Every Cloudflare skill in one command

Installs into ~/.claude/skills/. Add --project after -- to install into the current repository.

curl -fsSL https://claudeskills.page/install.sh | sh -s -- cloudflare-workers hono-edge s3-object-storage supabase-backend http-caching sveltekit-apps netlify-deploys vercel-deploys connection-pooling bot-fraud-defense

Cloudflare skills FAQ

What is the best Claude Code skill for Cloudflare?

Start with Cloudflare Workers: Right storage per binding, typed env, one-command rollback. Then add Hono on the Edge and S3 and R2 Object Storage, which cover the next most common Cloudflare requests.

How do I install all 10 Cloudflare skills at once?

Pass every name to the installer in one command: curl -fsSL https://claudeskills.page/install.sh | sh -s -- cloudflare-workers hono-edge s3-object-storage supabase-backend http-caching sveltekit-apps netlify-deploys vercel-deploys connection-pooling bot-fraud-defense. Add --project to install them into the current repository's .claude/skills/ folder so your team gets them too.

Do these Cloudflare skills work outside Claude Code?

Yes. Each skill uses only the portable Agent Skills frontmatter, so the same folder works on claude.ai, through the Claude API and in the Agent SDK. Skills that run bundled scripts need an environment with code execution.

esc