agentleFS
MelvynxMelvynx/ai-maxxing-skills/skills/setup-cloudflare/SKILL.md

setup-cloudflare

Skill32 starsChanged 23 days agoMITView on GitHub

Install the official Cloudflare CLI (cf) on macOS, Linux or Windows, sign the user in through the browser and pick their account, so the agent can manage domains, DNS and deploys. Use when cf is missing, the user wants to connect Cloudflare, or cf auth whoami is not authenticated.

  • Installs packages

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If you got this skill from a link instead of a local folder, install nothing else from the repo: fetch a file only when a step needs it, …

    line 8
  2. Very specific:

    Make sure Node works (node --version, v20 or higher).

    line 10
  3. Distinctive:

    If the user has no Cloudflare account, send them to https://dash.cloudflare.com/sign-up and wait for "done".

    line 11
  4. Very specific:

    Run cf accounts list. With more than one account, ask which one to use and add export CLOUDFLARE_ACCOUNT_ID=<id> to the user's shell config …

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Connect the user's Cloudflare account to the cf CLI so the agent handles domains, DNS and deploys without the user opening the dashboard. Do every step yourself and only ask for what needs a human (creating the account, approving the login, buying a domain). Talk to the user in their language, short messages, no jargon (never say "CLI", "OAuth" or "zone" to them). Never use Wrangler and never ask for an API token.

If you got this skill from a link instead of a local folder, install nothing else from the repo: fetch a file only when a step needs it, with curl -fsSL https://raw.githubusercontent.com/Melvynx/ai-maxxing-skills/main/skills/setup-cloudflare/<path> -o <scratch>/<file>, and read another skill it names only when you reach it, from https://raw.githubusercontent.com/Melvynx/ai-maxxing-skills/main/skills/<skill-name>/SKILL.md.

  1. Make sure Node works (node --version, v20 or higher); if not, run the setup-node skill first.
  2. If the user has no Cloudflare account, send them to https://dash.cloudflare.com/sign-up and wait for "done". The free plan is enough.
  3. Install the CLI with npm install -g cf, then check cf --version.
  4. If cf auth whoami already says "authenticated": true, skip to step 5. Otherwise run cf auth login in the background with its output in a file. It opens the browser: tell the user to sign in, approve every permission including the sensitive ones (deploys and DNS need them), and say "done". If no browser opens, read the link from the output file and give it to them. Check cf auth whoami until it says authenticated.
  5. Run cf accounts list. With more than one account, ask which one to use and add export CLOUDFLARE_ACCOUNT_ID=<id> to the user's shell config (~/.zshrc or ~/.bashrc, on Windows a user environment variable) so every session uses it.
  6. Run cf zones list to see their domains. If they have none, tell them they can buy one in Cloudflare (Domain Registration, at cost price) or keep one from another registrar and move its name servers to Cloudflare later; the create-* skills handle that when they need a domain. Never buy a domain for them.
  7. Prove it: cf auth whoami is authenticated on the right account, cf zones list answers (with their domains or none yet), and a new session finds cf too ($SHELL -lic 'cf --version').

End with a short check list, a check or a cross on each line: Node works, cf installed, signed in, account picked, domains found (list them or say none yet). Then tell the user in one line that the agent can now manage their domains and put sites live on Cloudflare.

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.