agentleFS
Sign inStart free
MelvynxMelvynx/ai-maxxing-skills/skills/cloudflare/SKILL.md

cloudflare

Skill32 starsChanged 24 days agoMITView on GitHub

Run every Cloudflare job through the official `cf` CLI - domains, DNS, Workers deploys, secrets and custom domains, KV, D1, R2, WAF, SSL and cache. Use when the user mentions Cloudflare, cf, DNS, a domain, deploy, Workers, KV, D1, R2, CDN, SSL or cache.

  • Installs packages

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

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

  • 0

    Common

    Most of the 59 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the official cf CLI (npm i -g cf) for every Cloudflare action.

    line 6
  2. Very specific:

    When cf stops with "More than one account available", run cf accounts list and export CLOUDFLARE_ACCOUNT_ID=<id> for the session.

    line 14
  3. Very specific:

    Every mutating command accepts --dry-run.

    line 37
  4. Very specific:

    When another service (Lumail, Stripe, Google, a mail provider) shows DNS records to add, create each one exactly as given (type, name, …

    line 39

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use the official cf CLI (npm i -g cf) for every Cloudflare action. Never Wrangler, an S3 SDK script or raw calls to api.cloudflare.com; if cf cannot do something, say so and stop. The Cloudflare connector in Claude can help for reads, but changes go through cf.

cf --version                 # missing: run the setup-cloudflare skill
cf auth whoami               # must say "authenticated": true
cf auth login                # OAuth in the browser, the user grants every scope, sensitive ones included

When cf stops with "More than one account available", run cf accounts list and export CLOUDFLARE_ACCOUNT_ID=<id> for the session. Zone commands take -z <domain or zone id>. Never print tokens or read the cf config file.

Find any command instead of guessing it, with generic queries (action + resource type, no names or ids):

cf cli search "<what you want to do>"     # JSON matches
cf <discovered command> --help              # flags of that command
cf schema <command without the leading cf>  # exact API request body

The commands used most:

cf zones list
cf dns records list -z <domain>
cf dns records create -z <domain> --body '{"type":"CNAME","name":"www","content":"target","proxied":true}'
cf init <dir> && cf dev        # then cf build, cf deploy
cf r2 buckets list
cf r2 objects put <key> --bucket-name <bucket> --file <path> --content-type <mime>

Everything else (DNS update or delete, Worker custom domain, secrets, routes, crons, KV, D1, cache purge, SSL, WAF, Access, email routing, DNSSEC, analytics) goes through cf cli search "<job>". Add --local to simulate KV, D1 and R2 objects. Subcommand names follow the CLI release: if one errors, search it.

Every mutating command accepts --dry-run. Confirm with the user before anything destructive (DNS deletes, zone changes, purges), and pass --force only after their yes.

When another service (Lumail, Stripe, Google, a mail provider) shows DNS records to add, create each one exactly as given (type, name, content, priority, TTL), keep mail and verification records unproxied ("proxied": false), then list the zone to confirm they exist.

Download now (ZIP)

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