agentleFS
fmindfmind/dotfiles/skills/cf/SKILL.md

cf

Skill13 starsChanged yesterdayMITView on GitHub

Inspect and manage Cloudflare zones, DNS, Workers, Pages, R2, D1, and Zero Trust with cf.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • fmind/dotword for word, first seen Nov 15, 2026

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Keep secrets out of argv: avoid --text ...; write a 0600 temp JSON file (or use dot secret run) and apply cf -q workers secrets bulk …

    line 34
  2. Very specific:

    Piped cf deploy skips prompts: never pipe stdin accidentally into cf deploy.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Cloudflare (cf)

Manage Cloudflare accounts, DNS, Workers, Pages, R2, D1, and Zero Trust via cf (CF_SEND_TELEMETRY=0 is set globally in fmind/dot; run cf cli telemetry disable on unconfigured hosts).

Commands

cf -q auth whoami
cf -q auth list
cf -q zones list
cf -q docs search "workers secrets"
cf -q cli search "workers secrets"
cf -q schema workers secrets update
  • Pin account and zone: pass --profile <name> and -z <zone-id-or-domain> (or cf auth activate <profile>) on customer work so writes cannot hit the wrong account; prefer cf auth login --use-keyring for token storage.
  • Quiet and JSON output: pass -q (CF_QUIET=1) to suppress update banners; cf emits machine-readable JSON on stdout by default on supported commands.
  • Discover safely: query offline CLI help (cf -q cli search), payload schemas (cf -q schema), and docs (cf -q docs search), and test mutations with --dry-run or --local.

Secrets and Guardrails

  • Keep secrets out of argv: avoid --text ...; write a 0600 temp JSON file (or use dot secret run) and apply cf -q workers secrets bulk --worker <script> --secrets @<tmpfile>, then shred/remove the temp file.
  • Piped cf deploy skips prompts: never pipe stdin accidentally into cf deploy; require explicit approval before DNS, Workers/Pages deploys, cache purges, R2/KV/D1 writes, Zero Trust/WAF rules, billing reads/writes, api writes, or -y.

Documentation

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.