Build Packs
    Claude Code
    Intermediate

    Domain Autopilot

    idle domains on cloudflare's free plan, a real page, and a reminder before they expire

    Cover art for the Domain Autopilot Build Pack
    Install 2 min; about 15 min per domain, most of it waiting for nameservers
    $0: Cloudflare free plan and free Workers tier. You only pay your registrar's renewal
    1 prompts
    v0.1.1
    claude-code
    cloudflare
    python
    godaddy

    A Claude Code skill that sorts your domains by where they point, moves the idle ones to Cloudflare's free plan with a designed coming-soon page, proves the page is live over HTTPS, and lists every expiry date with 60, 30 and 7 day reminders.

    What you build

    PartWhat it isWhat it does
    The sorterclassify, reading nameservers from Google Public DNS and probing ports 80 and 443Labels each domain so anything on Vercel, Shopify, Cloudflare or a live site is left alone
    The zoneA Cloudflare zone on the free planCreated only for domains marked ready; the old nameservers are saved for rollback
    The switchGoDaddy API, or the two nameservers printed for any other registrarPoints the domain at Cloudflare; one command puts the old ones back
    The pageA Cloudflare Worker with a designed coming-soon pageServed on apex and www, with your text and color from brands.json
    The proofA unique marker in the page, fetched over HTTPSSays live only when both hosts return the marker
    The calendarExpiry dates from RDAPPrints reminder dates 60, 30 and 7 days before each renewal

    Status: built, and we need your test

    The skill is written, reviewed twice, and its read-only commands ran against real public DNS and RDAP data. The commands that change your accounts (creating the Cloudflare zone, switching nameservers, deploying the page) were checked line by line against the Cloudflare and GoDaddy docs but have not yet been run end to end on a real account. Try it on one spare domain first and post in the community what happened.

    A clay robot in a hard hat finishing a house whose front is a flower-shop website

    Where this comes from

    A post went around describing an agent wired to Namecheap and Cloudflare: it reads every domain in the account, puts the idle ones on Cloudflare's free plan, puts up a coming-soon page, checks HTTPS, and pings you when it is live. Good idea, but tied to one registrar and one person's setup. This is the version anyone can install: registrar neutral, every change behind a dry run, and a page that looks designed instead of a white screen with two words. The page follows the visual rules of the landing-page-design skill from elayadesign/ai-design-skills (MIT), included in the zip. Built by Hector Diaz for the AI Auto Base community, with Claude Code.

    What you build

    You install the skill once. Then you tell Claude "check my domains" with a list, and it shows you where each one points today. For each domain marked ready you say "put it on Cloudflare", read the dry run, and say apply. Claude creates the zone, switches the nameservers (by API on GoDaddy, or hands you the two values to paste at any other registrar), deploys the page, and keeps checking until the page answers over HTTPS on both the bare domain and www.

    What it deliberately does not do: it never transfers a domain, never buys one, never copies anything from an old host, and never touches a domain that already serves a site unless you force it and confirm. Every nameserver change can be undone with one command.

    Do you need this? Be honest first

    This is for you if you own a handful of domains that sit parked at the registrar or on a hosting plan you pay for only to show "coming soon", and you want them on a free plan with a page that does not embarrass you.

    Close the tab if your domains already run real sites, or if you have one domain and five minutes: clicking through Cloudflare's dashboard once is faster than installing anything.

    What you need

    • The machine. Any Windows, Mac or Linux computer with Claude Code and Python 3.9 or newer. No packages to install.
    • The accounts. A free Cloudflare account with an API token (the exact permissions are in the README) and your account id. A GoDaddy Personal Access Token only if your domains are at GoDaddy.
    • The time. Two minutes to install. About fifteen minutes per domain, most of it waiting for the nameserver change to spread.

    What is in the zip

    domain-autopilot/
      SKILL.md           the instructions Claude follows: every command, every class, the env vars
      domains.py         the whole tool, Python standard library only, dry run unless --apply
      design.md          the visual rules the page follows (elayadesign, MIT)
      README.md          install in two minutes, what you need, what it changes
      CREDITS.md         who built it, what was verified and what was not
      DISCLAIMER.md      as is, no warranty, use at your own risk
      LICENSE            MIT for SKILL.md and domains.py
      LICENSE-design.md  MIT for design.md
    

    The same files are on GitHub: AIAutoBase/domain-autopilot-skill.

    What was verified and what was not

    Verified on Windows 11 with Python 3.14: the offline self-check (classification, hostname validation, HTML escaping, color and link checks), and the read-only commands against live data, classify through Google Public DNS, expiry through rdap.org, and the zone step in dry run. Codex reviewed every API call against the official Cloudflare, GoDaddy, Google Public DNS and RDAP docs and found eight problems, including a missing DNS record that would have kept the page from ever loading. A second Claude model confirmed and fixed all eight.

    Not verified: zone, ns and finish with --apply on a real Cloudflare or GoDaddy account, and installing the skill on a clean machine and asking Claude for it in plain words. Those are where your reports help most.

    Read the skill before you install it

    Open SKILL.md and domains.py before you copy the folder into your skills. Hand them to Claude and ask what they will change in your Cloudflare and registrar accounts. The answer should be: one zone per domain, two proxied DNS records, one Worker and two routes, and a nameserver change at the registrar, all only after you add --apply.

    More packs