agentleFS
Sign inStart free
iansteitz1-engiansteitz1-eng/aria-skills/cloudflare-dns-deploy/SKILL.md

cloudflare-dns-deploy

Skill0 starsChanged 2 months agoApache-2.0View on GitHub

Reconcile DNS records from a declared YAML catalog to Cloudflare via the API, and optionally run the companion nginx + certbot bootstrap for records pointing at your server. Idempotent. --dry-run by default, --apply hits the API, --server-setup also wires nginx + obtains Let's Encrypt cert. Use when the user says "deploy DNS", "add a subdomain", "stand up <X>.example.com", or before any subdomain launch.

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:

    Default is dry-run: No API write until --apply.

    line 34
  2. Very specific:

    Server-setup is opt-in: Default --apply only touches Cloudflare.

    line 36

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

YAML → Cloudflare DNS → nginx → certbot, in one command.

When to use

  • New subdomain launches (replaces dashboard click + SSH + nginx + certbot dance)
  • DNS audits (--dry-run shows drift between YAML and live)
  • Multi-zone management (one YAML covers all your zones)
  • Pruning stale records (--prune deletes A/AAAA/CNAME/TXT/MX not in YAML)

How it works

  1. Reads dns_records.yaml
  2. For each zone, lists current Cloudflare records
  3. For each declared record: matches by (zone, type, name). Creates if absent; patches if drift in content/TTL/proxied.
  4. With --server-setup: waits for DNS propagation, enables nginx site, runs certbot, verifies HTTPS.

Env vars required

VarRequired forNotes
CLOUDFLARE_API_TOKENallScoped Token (Zone:Read + DNS:Edit on target zones)

Token creation: dash.cloudflare.com → My Profile → API Tokens → Create Token → "Edit zone DNS" template.

Safety

  • Default is dry-run. No API write until --apply.
  • Doesn't delete by default. --prune is the explicit opt-in to remove records.
  • Server-setup is opt-in. Default --apply only touches Cloudflare; you don't accidentally invoke certbot.
  • Cert renewal stays under certbot.timer — this skill issues; renewal is automatic via the system service.

Hosted version

Vox Ordo runs this with:

  • Multi-zone team management
  • Scheduled drift checks (alerts on manual dashboard changes)
  • Approval workflow for --prune and --server-setup
  • Free tier · BYOK · no credit card

License

Apache 2.0

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