domain-dns-ops — Claude Code skill: DNS and install
The domain-dns-ops skill guides domain, Cloudflare zone, and redirect work. Use it when setting up a domain and checking DNS or HTTPS behavior.
MIT 192 installs ★ 7,554 updated 2026-10-20
npx skills add steipete/agent-scripts --skill domain-dns-ops -a claude-codeWhat domain-dns-ops does
The skill routes domain operations through ~/Projects/manager, treating its documents, scripts, and checklists as the working source of truth. It covers choosing Page Rules, Rulesets / Bulk Redirects, or a Worker, then creating a Cloudflare zone, changing nameservers, and adding DNS records needed for HTTPS.
It verifies DNS with dig +short example.com @1.1.1.1 and checks an HTTPS redirect with curl -I https://example.com, expecting 301. Namecheap delegation uses bin/namecheap-set-ns; Worker redirects use the mapping file and route instructions. Confirm the registrar before investigating “invalid nameservers”. Changes under ~/Projects/manager also need a commit in that repository.
What it helps with
- set up a new Cloudflare domain zone
- choose a redirect model for a domain
- change Namecheap nameservers
- verify DNS with
dig - check an HTTPS redirect returning
301
Example prompts for the agent
- Set up this domain through Cloudflare using
~/Projects/manager/DNS.md, then verify DNS and HTTPS. - Check the domain’s registrar, configure its nameservers, and run
dig +short example.com @1.1.1.1. - Update the Worker redirect from
~/Projects/manager/redirect-worker-mapping.md, bind its route, and testcurl -I https://example.com.
How to install domain-dns-ops
1Skills CLI (Vercel)
npx skills add steipete/agent-scripts --skill domain-dns-ops -a claude-code2Manually: put the files in place
~/.claude/skills/domain-dns-ops/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/domain-dns-ops/
1Skills CLI (Vercel)
npx skills add steipete/agent-scripts --skill domain-dns-ops -a codex2Manually: put the files in place
.agents/skills/domain-dns-ops/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add steipete/agent-scripts --skill domain-dns-ops -a cursor2Manually: put the files in place
.cursor/skills/domain-dns-ops/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install steipete/agent-scripts skills/domain-dns-ops2Manually: put the files in place
.github/skills/domain-dns-ops/SKILL.md1Skills CLI (Vercel)
npx skills add steipete/agent-scripts --skill domain-dns-ops -a gemini-cli2Platform CLI
gemini skills install https://github.com/steipete/agent-scripts --path skills/domain-dns-opsManually: put the files in place
.devin/skills/domain-dns-ops/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add steipete/agent-scripts --skill domain-dns-ops -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about domain-dns-ops
How do I install domain-dns-ops in Claude Code?
Run npx skills add steipete/agent-scripts --skill domain-dns-ops -a claude-code, then check ~/.claude/skills/domain-dns-ops/SKILL.md.
What does domain-dns-ops do?
It guides registrar, Cloudflare zone, nameserver, DNS record, and redirect operations. It also runs DNS and HTTPS checks based on the procedures in ~/Projects/manager.
What should I check before debugging invalid nameservers?
Confirm the domain’s registrar first. Namecheap and DNSimple use different delegation steps.
Source text
SKILL.md · MIT
---
name: domain-dns-ops
description: "DNS/domain ops: registrars, zones, redirects, DNS/HTTP verify, manager truth."
---
# Domain/DNS Ops (Peter)
This skill is a thin router: use `~/Projects/manager` as truth, run the repo scripts, follow the checklists.
## Source of truth (read first)
- `~/Projects/manager/DOMAINS.md` (domain -> target map; registrar hints; exclusions)
- `~/Projects/manager/DNS.md` (Cloudflare onboarding + DNS/redirect checklist)
- `~/Projects/manager/redirect-worker.ts` + `~/Projects/manager/redirect-worker-mapping.md` (worker redirects)
## Golden path (new vanity domain -> Cloudflare -> redirect)
1. **Decide routing model**
- Page Rule redirect (small scale, per-zone).
- Rulesets / Bulk Redirects (account-level; needs token perms).
- Worker route (fallback; uses `redirect-worker`).
2. **Cloudflare zone**
- Create zone (UI), then confirm with `cli4`:
- `cli4 --get name=example.com /zones`
3. **Nameservers**
- If registrar = Namecheap: `cd ~/Projects/manager && source profile && bin/namecheap-set-ns example.com emma.ns.cloudflare.com scott.ns.cloudflare.com`
- If registrar = DNSimple: see `~/Projects/manager/DNS.md` for delegation API notes.
4. **DNS placeholders (so CF can terminate HTTPS)**
- Proxied apex `A` + wildcard `A` → `192.0.2.1` (see `~/Projects/manager/DNS.md` for exact `cli4` calls).
5. **Redirect**
- If using Page Rules: use the `cli4 --post ... /pagerules` template from `~/Projects/manager/DNS.md`.
- If using Worker: update mapping (`~/Projects/manager/redirect-worker-mapping.md`), deploy/bind routes per `~/Projects/manager/DNS.md`.
6. **Verify**
- DNS: `dig +short example.com @1.1.1.1` (expect CF anycast).
- HTTPS redirect: `curl -I https://example.com` (expect `301`).
## Common ops
- **Cloudflare token sanity**: follow the root secret rule; export only the needed Cloudflare token for one command.
- **Disable “Block AI bots”**: `cd ~/Projects/manager && source profile && bin/cloudflare-ai-bots status` / `bin/cloudflare-ai-bots disable`.
## After edits (commit/push)
If you changed anything in `~/Projects/manager` (docs, worker, scripts, mappings): commit there too.
1. Review: `cd ~/Projects/manager && git status && git diff`
2. Stage: `git add <paths>`
3. Commit (Conventional Commits): `git commit -m "feat: …"` / `fix:` / `docs:` / `chore:`
4. Push only when explicitly asked: `git push origin main`
## Guardrails
- Don’t touch `.md` lore domains or `steipete.md` unless explicitly asked; check `~/Projects/manager/DOMAINS.md`.
- Confirm registrar before debugging CF “invalid nameservers” (often “wrong registrar”).
- Prefer reversible steps; verify after each change (NS → DNS → redirect).
© steipete · MIT · steipete/agent-scripts