agentleFS
Simple-With-UsSimple-With-Us/BotFleet/.claude/skills/dns-and-registrars/SKILL.md

dns-and-registrars

Skill4 starsChanged 4 days agoApache-2.0View on GitHub

Fleet DNS and registrar playbook. Cloudflare is DNS for every fleet domain; registrar and Cloudflare account are separate. Usage.Jays.Services is a Cloudflare account name, not the hostname usage.jays.services. Create a new zone for each app apex on that account. Use when adding a domain, linking a host, choosing a Cloudflare account, or touching nameservers. Do not buy domains, mint accounts, or enable paid Cloudflare products without Jay.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not change DNS, buy domains, mint Cloudflare accounts, install products, or spend without Jay.

    line 19
  2. Distinctive:

    If an app later needs extra Cloudflare services, create a dedicated Cloudflare account for that app and migrate its zone(s) there.

    line 39
  3. Distinctive:

    After registration, point nameservers at Cloudflare and manage records in the app's own zone on the correct Cloudflare account.

    line 58
  4. Distinctive:

    Do not mint Cloudflare accounts, buy domains, or enable paid Cloudflare products without Jay.

    line 68

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fleet DNS and Registrars (ALL AGENTS)

Shared ~/.claude/skills. Monet, Claude/Fable, and (when active) Renoir all load this directory. Do not treat the word Monet in examples as proof of your seat. Pin AGENT_SEAT / AGENT_TAG from the logged-in account before Slack or board --by:

  • Monet → MONET, Notes Monet, monet/, ~/apps/<app>-monet
  • Claude / Fable → CLAUDE, Notes Claude, claude/, ~/apps/<app>-claude
  • Renoir → RENOIR, Notes Renoir, renoir/, ~/apps/<app>-renoir Cursor, Grok, Grok Bot, Codex, AG, DeepSeek, Kimi, and Fx have their own skill dirs and must not take identity from here.

Cloudflare is the DNS manager for every fleet domain. Registrar and Cloudflare account are separate.

Canonical: docs/DNS-AND-REGISTRARS.md in ai-fleet-coordinator.

Do not change DNS, buy domains, mint Cloudflare accounts, install products, or spend without Jay.

Account vs zone vs hostname

Usage.Jays.Services is a Cloudflare account name (login mail@jays.services). It is not a zone and not a hostname. usage.jays.services is an already-live hostname. jays.services is an existing DNS-only zone on that same account.

A new app such as ContactLogo gets its own new Cloudflare zone for that apex (contactlogo.com), created on account Usage.Jays.Services. Do not put ContactLogo — or any new app — records on usage.jays.services or jays.services.

TermExample
AccountUsage.Jays.Services
New zonecontactlogo.com on that account
Do not use as the new-app zoneusage.jays.services, jays.services

Default for a new DNS-only zone

App hosted on Vercel, Coolify, or elsewhere, with no Workers / R2 / WAF / other Cloudflare products: create a new zone for that app's apex on the Usage.Jays.Services account. That account already holds Usage-Monitor plus DNS-only zones jaywedgeworth.com and jays.services.

Example (ContactLogo): add zone contactlogo.com on account Usage.Jays.Services, then move Namecheap nameservers (dns1.registrar-servers.com / dns2.registrar-servers.com) to the nameservers Cloudflare shows for that new zone.

If an app later needs extra Cloudflare services, create a dedicated Cloudflare account for that app and migrate its zone(s) there. Do not pile product services onto the Usage.Jays.Services account.

Cloudflare accounts

AccountLoginHoldsDo not
Usage.Jays.Servicesmail@jays.servicesUsage-Monitor + DNS-only zones + new app zones (each app's own apex)Put ST/CT product services here. Do not attach new-app records to usage.jays.services or jays.services.
SocraticTrade.comsocratic.trade@jays.servicesST registrar for SocraticTrade.com and Socratic.Trade, ST DNS, ST R2 weekly backupsMove unrelated new zones here
Congress.Tradecongress.trade@jays.servicesCT DNS, CT R2 weekly backupsMove unrelated new zones here
oldunused Gmail login (do not print it)unusedCreate or move anything here. Leave it.

Registrars

RegistrarUse for
NamecheapDefault for most domains. NAMECHEAP_API_KEY lives in global API keys (do not print or commit it).
UnstoppableDomainsjays.services only
Cloudflare registrarSocraticTrade.com and Socratic.Trade only (the ST Cloudflare account)

After registration, point nameservers at Cloudflare and manage records in the app's own zone on the correct Cloudflare account. Do not leave a live product on Namecheap parking / URL Forward.

Linking a domain

  1. Confirm host + required records on the app's own zone.
  2. Confirm that zone is on the right Cloudflare account (Usage.Jays.Services unless the app already has a dedicated account).
  3. Change DNS at Cloudflare unless nameservers are still at the registrar (then move NS first).
  4. On an NS move, copy existing MX onto the new Cloudflare zone (Namecheap mail is often eforward*.registrar-servers.com). Missing MX kills mail. Do not copy URL Forward or parking CNAMEs (parkingpage.namecheap.com).
  5. Cloudflare orange-cloud (proxied) hides the origin from HTTP-01. Issue the first cert grey-cloud (DNS only) or use a Cloudflare origin cert, then proxy. Preferred end state: proxied A/CNAME like host.jays.services.

Do not mint Cloudflare accounts, buy domains, or enable paid Cloudflare products without Jay. Env/secrets stay with Meteorologist.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.