namecheap-domain-dns-ops

Inspects repo domain signals and produces DNS operations plans for Namecheap-registered domains.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/gmackie/agent-skills --skill namecheap-domain-dns-ops-gmackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: namecheap-domain-dns-ops
Source: https://github.com/gmackie/agent-skills/tree/main/skills/namecheap-domain-dns-ops
Command: npx skills add https://github.com/gmackie/agent-skills --skill namecheap-domain-dns-ops-gmackie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, jq, ripgrep, and includes scripts (resource) and references (resource) components.

What problem does it solve? Teams often confuse registrar tasks with DNS hosting tasks, editing Namecheap host records when the domain is actually delegated to custom nameservers, or breaking verification and email records during cutovers. This Skill inventories the domain and DNS surface visible in a repo and turns it into a concrete, reviewable DNS operations plan. ## Core Features & Use Cases - Domain Surface Inventory: Scans env files, docs, and config for domain names, DNS-provider markers, and record patterns like A, CNAME, TXT, MX, and CAA using a bundled shell script. - Control-Plane Verification: Distinguishes whether DNS is managed via Namecheap BasicDNS, FreeDNS, or PremiumDNS versus delegated to a third-party DNS provider. - Cutover Risk Review: Identifies apex and www routing needs, email and verification records, certificate or CAA requirements, and nameserver-change risks before any change is made. - Use Case: Before migrating a site to a new host, run the inspection script against the project repo, confirm where DNS is actually controlled, and generate a dated ops plan under docs/infrastructure listing missing records and next steps. ## Quick Start Ask the assistant to inspect this repository's domain and DNS surface and produce a Namecheap DNS operations plan with cutover risks and next steps.

Frequently Asked Questions about namecheap-domain-dns-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if DNS is managed at Namecheap or elsewhere?▼

Check whether the domain uses Namecheap BasicDNS, FreeDNS, or PremiumDNS, or whether it is delegated to custom nameservers. If custom nameservers are set, DNS records must be changed at the third-party DNS provider, not in the Namecheap panel.

How to plan a DNS cutover for a Namecheap-registered domain?▼

Start by inventorying domain names and record patterns in the repo with the inspection script, then review apex and www routing, email and verification records, and CAA needs. Write a plan covering the current surface, control-plane review, risks, and next steps.

What is the difference between nameserver changes and host-record changes?▼

Host-record changes edit individual A, CNAME, TXT, or MX records at the current DNS provider, while a nameserver change moves all DNS hosting to a new provider. Changing nameservers without recreating required records on the new provider wipes existing DNS assumptions.

Can I use a CNAME record at the apex domain?▼

CNAME usage at the apex depends on the DNS provider's model, since standard DNS does not allow CNAME at the root. Verify the provider's apex handling before planning, as some providers offer ALIAS or flattening workarounds.

What are common mistakes when managing Namecheap DNS?▼

Common mistakes include editing Namecheap host records when the domain uses custom nameservers, planning apex CNAMEs without checking provider support, changing nameservers without recreating records, and mixing registrar tasks with DNS-hosting tasks.