agentleFS
Sign inStart free
ejc3ejc3/claude-skills/cloudflare/SKILL.md

cloudflare

Skill1 starsChanged 25 days agoNo licenceView on GitHub

Build, move and run a site on Cloudflare Workers. Moving a Next.js site from Vercel to Cloudflare Workers, or running it on both while it moves. A feature-by-feature map from Vercel to Cloudflare (OpenNext, wrangler.jsonc, env and secrets, previews, cron, storage, ISR caches, images, middleware and proxy, waitUntil and after, OIDC, client-IP headers, firewall and Access, logs, domains and TLS, size and runtime limits) with the gotchas that break a site only on Workers; a staged strategy from a protected staging Worker to a domain cutover with one-step rollback; pre- and post-cutover checklists; how to run several site conversions at once without them colliding; and lessons from a move made under a deadline (data keyed by VERCEL_ENV, per-environment builds, migrations, cron time limits, Marketplace storage). Running on Workers: the traps that break a Worker only in production, with Turso/libSQL as the worked case (I/O or promises shared across requests hang every later request in an isolate, outbound calls need a timeout, pages must not wait for ever, reading Workers Logs to tell a hang from an error, shipping a fix during an outage past branch rules and a busy CI pool) in workers-gotchas.md. Use when writing or reviewing Worker code that talks to a database or another API, when a Worker request hangs or is canceled, when diagnosing an outage from Workers Logs, when porting a Vercel site to Cloudflare, adding a Cloudflare deploy beside Vercel, planning or executing a domain cutover, or coordinating several such moves.

  • Reads credentials
  • Sends data out

69 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use nextjs-on-cloudflare, basin and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CloudflareSkill

    nextjs-on-cloudflare

    Build, migrate, and deploy Next.js apps on Cloudflare Workers with vinext. Use when starting a Next.js project on Cloudflare, moving an existing app to Workers, choosing between vinext and OpenNext, or setting up vinext for Workers. For setup, migration, or deployment, install vinext's upstream skills with `npx skills add cloudflare/vinext` if missing, then read and follow the applicable skill and docs.

    Also in 5 projects that use this

  • CloudflareSkill

    basin

    Build and troubleshoot Cloudflare Basin analytics workflows with Basin Pipelines, Basin Catalog, and Basin SQL. Use for streaming data into R2 Iceberg tables, managing catalogs, or querying those tables; also use for requests using the former Data Platform, Pipelines, R2 Data Catalog, or R2 SQL names.

    Also in 5 projects that use this

  • hoodiniSkill

    analytics-metrics

    Build data visualization and analytics dashboards. Use when creating charts, KPI displays, metrics dashboards, or data visualization components. Triggers on analytics, dashboard, charts, metrics, KPI, data visualization, Recharts.

    Also in 3 projects that use this

  • hoodiniSkill

    aws-account-management

    Manage AWS accounts, organizations, IAM, and billing. Use when setting up AWS Organizations, managing IAM policies, controlling costs, or implementing multi-account strategies. Triggers on AWS Organizations, AWS IAM, AWS billing, Cost Explorer, SCPs, multi-account, AWS SSO, Identity Center.

    Also in 3 projects that use this

  • OpenAISkill

    sandbox-sdk

    Build sandboxed applications for secure code execution. Load when building AI code execution, code interpreters, CI/CD systems, interactive dev environments, or executing untrusted code. Covers Sandbox SDK lifecycle, commands, files, code interpreter, and preview URLs. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

    Also in 10 projects that use this

  • +4 more from hoodini
  • +3 more from cloudflare

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 59 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 59 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free