How to use the Domain & DNS Ops agent skill

What an agent skill is and what this one does

An agent skill is a folder of instructions (a SKILL.md file plus optional reference files) that an AI agent loads when a request matches the skill's description. This skill does not contain DNS logic itself. Its SKILL.md acts as a thin router: it tells the agent to treat the ~/Projects/manager repository as the source of truth, run the scripts stored there, and follow the checklists in that repository.

• Decide the redirect model: Page Rule, Rulesets / Bulk Redirects, or a Worker route.
• Create the Cloudflare zone and confirm it with the cli4 tool.
• Point nameservers at Cloudflare, using bin/namecheap-set-ns for Namecheap or the notes in DNS.md for DNSimple.
• Add proxied placeholder A records (apex and wildcard) pointing to 192.0.2.1.
• Configure the redirect and verify it: dig for DNS, curl -I for an expected 301.
• Commit any changes made to the manager repo, pushing only when explicitly asked.

Install the skill from a ZIP file

Download the ZIP for domain-dns-ops from this page and unzip it. Then place the folder in one of these locations: your personal skills directory at ~/.claude/skills/, or a project-specific .claude/skills/ folder inside the project that needs it.

You can also upload the skill in the Claude apps under Settings → Capabilities → Skills.

• Personal install: unzip into ~/.claude/skills/.
• Project install: unzip into the project's .claude/skills/ folder.
• Claude apps: Settings → Capabilities → Skills, then upload the skill.

Prepare the manager repository before you use it

The skill points to files that are not included in the skill folder. Before it can do anything useful, you need a local ~/Projects/manager repository that contains DOMAINS.md, DNS.md, redirect-worker.ts, redirect-worker-mapping.md and a bin/ directory with the helper scripts. The reference file references/manager-repo.md lists these files and says that bin/namecheap-set-ns reads environment variables from a profile file in that repository.

You also need the cli4 command-line tool configured for Cloudflare API access, a Cloudflare API token with the permissions your task needs, Namecheap or DNSimple account access for nameserver changes, git, dig and curl.

• ~/Projects/manager with DOMAINS.md, DNS.md, redirect-worker.ts and bin/ scripts
• cli4 configured for Cloudflare API access
• Cloudflare API token with the required permissions
• Namecheap or DNSimple account access for nameserver changes
• git, dig and curl installed

Trigger the skill with natural requests

You do not need special syntax. Describe the domain work in plain language and mention Cloudflare, DNS, nameservers or redirects so the agent matches the skill. Name the domain and the outcome you want. The agent will then check DOMAINS.md for the domain's target and registrar before changing anything.

Good requests name a specific domain and a specific goal, for example asking to move a domain's nameservers to Cloudflare, set up a redirect to a target, or check what a domain currently resolves to.

• "Set up example.com on Cloudflare and redirect it to my main site."
• "Flip the nameservers for example.com to Cloudflare; it is registered at Namecheap."
• "Check whether example.com redirects over HTTPS with a 301."
• "Find example.com in my domain map and tell me its target and registrar."

Example workflow: a new vanity domain

Suppose you want a new vanity domain to redirect to an existing site. The skill's golden path starts by choosing a routing model, then creating the zone in the Cloudflare UI and confirming it with cli4 using the zone listing call. If the registrar is Namecheap, the agent runs the helper script from inside the manager repo after sourcing its profile file. Next it adds the placeholder records and configures the redirect using the templates in DNS.md. Finally it verifies DNS and the HTTPS redirect, checking each stage before moving on.

Run the routine Cloudflare checks

Besides new domains, the skill covers routine tasks. One common one is turning off Cloudflare's "Block AI bots" setting. The skill directs the agent to check status first and then disable, using the bin/cloudflare-ai-bots helper in the manager repo. The bot helper needs a token with the right permissions.

Safety notes for scripts and network access

This skill runs scripts and uses the network. The steps execute real registrar and Cloudflare commands, and a wrong nameserver or redirect change can take a site offline. The skill's own guidance is to prefer reversible steps and to verify after each change in the order NS, then DNS, then redirect.

The skill also tells the agent to export only the Cloudflare token needed for a single command, and to leave lore domains and steipete.md alone unless you explicitly ask. Review git status and git diff before any commit, and push only when you have asked for it.

• Review the planned command before the agent runs any registrar or Cloudflare change.
• If Cloudflare reports invalid nameservers, first confirm the registrar; the skill notes this is often a wrong-registrar problem.
• Do not change live DNS or nameservers without review.

Tips for getting reliable results

Keep DOMAINS.md accurate, because the agent uses it as the map from each domain to its target, registrar and exclusions. Use the search pattern from the reference file to find a domain quickly. If you do not keep a runbook repo with this layout, the skill will not give you a working setup by itself.

• Search the domain map: rg -n "\bexample\.com\b" ~/Projects/manager/DOMAINS.md
• Ask the agent to verify after every change rather than only at the end.
• Read DNS.md first if your registrar is DNSimple, since the skill defers those steps to it.