agentleFS
Sign inStart free
blitzhash360-webblitzhash360-web/blitzhash-cloudflare-production-skills/skills/cloudflare-dns-records/SKILL.md

cloudflare-dns-records

Skill0 starsChanged 11 days agoMITView on GitHub

List, add, update and delete Cloudflare DNS records and subdomains (A, AAAA, CNAME, TXT, MX, CAA) with dry-run plans and explicit confirmation. Use when the user wants to point a domain or subdomain at a host (Vercel, Netlify, Lovable, a VPS), fix a record, or toggle the orange-cloud proxy.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Run commands with npx -y github:blitzhash360-web/blitzhash-cloudflare-production-skills <command> or, inside a clone of the repo, node …

    line 8
  2. Very specific:

    Add any record: cf-skills dns add --type TXT --name @ --content "v=spf1 include:_spf.example.com ~all"

    line 14
  3. Very specific:

    Update (shows a before -> after diff): cf-skills dns update --name staging --type A --proxied true

    line 15
  4. Very specific:

    Every write command is a dry run by default.

    line 29
  5. Very specific:

    Only after that "yes", re-run the same command with --apply --yes (your shell is not interactive).

    line 30
  6. Distinctive:

    Never delete records or rules the user did not name.

    line 31
  7. Very specific:

    Run cf-skills audit before and after changes and tell the user what moved.

    line 32

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

Cloudflare DNS records and subdomains

Run commands with npx -y github:blitzhash360-web/blitzhash-cloudflare-production-skills <command> or, inside a clone of the repo, node bin/cf-skills.mjs <command>. Below, cf-skills means either. Zone is --zone <domain or zone id> or $CLOUDFLARE_ZONE_ID.

Commands

  • List: cf-skills dns list [--type CNAME]
  • New subdomain (type picked from the target): cf-skills dns subdomain --name app --target cname.vercel-dns.com --proxied false
  • Add any record: cf-skills dns add --type TXT --name @ --content "v=spf1 include:_spf.example.com ~all"
  • Update (shows a before -> after diff): cf-skills dns update --name staging --type A --proxied true
  • Delete: cf-skills dns delete --name old-landing --type CNAME

Guidance

  • Web records (A/AAAA/CNAME for the site) should normally be proxied (orange cloud) so the server IP stays hidden. Mail records must stay DNS-only.
  • Many app hosts (Vercel, Netlify and similar) ask for DNS-only CNAMEs or extra SSL settings when proxied; follow the host's custom-domain guide and say so.
  • A CNAME cannot share a name with other records; the script refuses and explains.
  • Adding a record that already exists is a no-op, so re-running is safe.
  • Token: Zone Read + DNS Edit, limited to the one zone.

Safety rules (always)

  • The API token lives only in the environment (CLOUDFLARE_API_TOKEN) or a git-ignored .env. Never ask the user to paste it into chat, never print it, never pass it as a flag, never commit it.
  • Every write command is a dry run by default. Run it without --apply first, show the user the printed plan, and wait for an explicit "yes" in chat.
  • Only after that "yes", re-run the same command with --apply --yes (your shell is not interactive). Never add --yes on your own initiative.
  • Never delete records or rules the user did not name. Never widen the token's permissions.
  • Run cf-skills audit before and after changes and tell the user what moved.

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