SkillsAdd

smithery/steipete

domain-dns-ops

DNS/domain ops: registrars, zones, redirects, DNS/HTTP verify, manager truth.

Installation

$ npx skills add smithery/steipete --skill domain-dns-ops
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

deploying-custom-domain-rest-api Similar name
aws/agent-toolkit-for-aws

Deploys a Regional REST API with a custom domain name, a Lambda backend function, and a request…

3.4K installs
domain-modeling Similar name
mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing o…

592.8K installs
convex-domains Similar name
get-convex/agent-skills

Point a domain you already own at your Convex app (DNS records, custom-domain attach, auth-orig…

18.3K installs
domain-driven-design Similar name
wondelai/skills

Model software around the business domain using bounded contexts, aggregates, and ubiquitous la…

5.7K installs
domain-authority-auditor Similar name
aaron-he-zhu/seo-geo-claude-skills

domain-authority-auditor — an installable skill for AI agents, published by aaron-he-zhu/seo-ge…

4.7K installs
seeker-domains Similar name
solana-mobile/solana-mobile-skills

Resolve and display .skr domain names in Solana mobile apps, in both directions between names a…

4.4K installs

Also in this package

Other skills from smithery/steipete.

npx skills add smithery/steipete
video-transcript-downloader 0 swiftui-view-refactor 0 swiftui-performance-audit 0 swiftui-liquid-glass 0 openai-image-gen 0 native-app-performance 0 markdown-converter 0 instruments-profiling 0

Browse all from smithery/steipete

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,739 B
  • docs SUMMARY.md 293 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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).

  1. Cloudflare zone

- Create zone (UI), then confirm with cli4: - cli4 --get name=example.com /zones

  1. 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.

  1. 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).

  1. 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.

  1. 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).