domain-dns-ops
Automates domain onboarding, nameserver updates, and redirect management using standardized infrastructure scripts.
Install
mkdir -p .claude/skills/domain-dns-ops && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2354" && unzip -o skill.zip -d .claude/skills/domain-dns-ops && rm skill.zipInstalls to .claude/skills/domain-dns-ops
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
DNS/domain ops: registrars, zones, redirects, DNS/HTTP verify, manager truth.Key capabilities
- →Onboard new zones to Cloudflare
- →Configure bulk redirects via Rulesets or Workers
- →Update nameservers at registrars like Namecheap or DNSimple
- →Verify DNS propagation and HTTPS status
- →Manage domain-to-target mappings
How it works
The skill acts as a router that executes scripts and follows checklists defined in a central project repository, ensuring all changes are tracked and verified.
Inputs & outputs
When to use domain-dns-ops
- →Onboard a new vanity domain to Cloudflare
- →Configure bulk redirects via Rulesets or Worker
- →Verify DNS propagation and HTTPS status
- →Update nameservers at Namecheap or DNSimple
About this skill
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
- Create zone (UI), then confirm with
- 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.mdfor delegation API notes.
- If registrar = Namecheap:
- DNS placeholders (so CF can terminate HTTPS)
- Proxied apex
A+ wildcardA→192.0.2.1(see~/Projects/manager/DNS.mdfor exactcli4calls).
- Proxied apex
- Redirect
- If using Page Rules: use the
cli4 --post ... /pagerulestemplate from~/Projects/manager/DNS.md. - If using Worker: update mapping (
~/Projects/manager/redirect-worker-mapping.md), deploy/bind routes per~/Projects/manager/DNS.md.
- If using Page Rules: use the
- Verify
- DNS:
dig +short example.com @1.1.1.1(expect CF anycast). - HTTPS redirect:
curl -I https://example.com(expect301).
- DNS:
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.
- 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
.mdlore domains orsteipete.mdunless 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).
When not to use it
- →Domains not managed within the ~/Projects/manager repository
- →Modifying .md lore domains without explicit instruction
Prerequisites
Limitations
- →Strictly bound to the ~/Projects/manager repository
- →Requires manual verification after each step
How it compares
It centralizes all domain operations into a single source of truth repository, replacing manual UI-based configuration with repeatable, versioned scripts.
Compared to similar skills
domain-dns-ops side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| domain-dns-ops (this skill) | 2 | 2mo | Review | Intermediate |
| bash-linux | 7 | 6mo | Review | Intermediate |
| create-worktree-skill | 2 | 9mo | No flags | Intermediate |
| moai-workflow-worktree | 0 | 2mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by steipete
View all by steipete →You might also like
bash-linux
davila7
Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.
create-worktree-skill
disler
Use when the user explicitly asks for a SKILL to create a worktree. If the user does not mention "skill" or explicitly request skill invocation, do NOT trigger this. Only use when user says things like "use a skill to create a worktree" or "invoke the worktree skill". Creates isolated git worktrees with parallel-running configuration.
moai-workflow-worktree
modu-ai
Git worktree management for parallel SPEC development with isolated workspaces, automatic registration, and seamless MoAI-ADK integration
k8s-operations
rohitg00
kubectl operations for applying, patching, deleting, and executing commands on Kubernetes resources. Use when modifying resources, running commands in pods, or managing resource lifecycle.
makefile-dev-workflow
raphaelmansuy
Unified development workflow for EdgeQuake using Makefile commands. Use when starting services, running tests, or managing the full development stack (database, backend, frontend). Provides simplified alternatives to raw cargo/npm commands.
worktree-manager
p3nGu1nZz
Manages git worktrees for worker containers (create/remove/cleanup). Use when setting up parallel work, repairing worktree state, or cleaning up stale worktrees.