How do I install the Domain Dns Ops skill?

Run npx skillmds@latest add kbarbel640-del/domain-dns-ops in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Domain Dns Ops safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Domain Dns Ops?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Domain Dns Ops free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Domain Dns Ops?

kbarbel640-del (@kbarbel640-del) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Domain Dns Ops by kbarbel640-del — Agent Skill

Name: Domain Dns Ops
Rating: 4.666666666666667 (3 reviews)
Author: kbarbel640-del

Domain Dns Ops

Domain/DNS ops across Cloudflare, DNSimple, Namecheap for Peter. Use for onboarding zones to Cloudflare, flipping nameservers, setting redirects (Page Rules/Rulesets/Workers), updating redirect-worker mappings, and verifying DNS/HTTP. Source of truth: ~/Projects/manager.

kbarbel640-del Updated Sep 8, 2026 1 repo stars

File contents

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)

Decide routing model
- Page Rule redirect (small scale, per-zone).
- Rulesets / Bulk Redirects (account-level; needs token perms).
- Worker route (fallback; uses redirect-worker).
Cloudflare zone
- Create zone (UI), then confirm with cli4:
  - cli4 --get name=example.com /zones
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.
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).
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.
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: source ~/.profile (prefer CLOUDFLARE_API_TOKEN; CF_API_TOKEN fallback).
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.

Review: cd ~/Projects/manager && git status && git diff
Stage: git add <paths>
Commit (Conventional Commits): git commit -m "feat: …" / fix: / docs: / chore:
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).

---name: domain-dns-opsdescription: Domain/DNS ops across Cloudflare, DNSimple, Namecheap for Peter. Use for onboarding zones to Cloudflare, flipping nameservers, setting redirects (Page Rules/Rulesets/Workers), updating redirect-worker mappings, and verifying DNS/HTTP. Source of truth: ~/Projects/manager.---# 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**: `source ~/.profile` (prefer `CLOUDFLARE_API_TOKEN`; `CF_API_TOKEN` fallback).- **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).

Frequently asked questions