Domain search

Skill thattimc/skills/skills/domain-search

Claude Code skills marketplace: domain-search + ssr-market-research (also usable as plain skill folders in Codex/Cursor)

Install

npx -y skills add thattimc/skills --skill domain-search

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Check domain-name availability and brainstorm brandable names to buy. Use when the user wants to know if a domain is available/taken, find an available name for a project, compare names across TLDs (.com/.ai/.io/...), or pick a product/company/brand name. Triggers: "is X.com available", "find a domain", "check these domains", "available domain names", "name this project/product/company", "brainstorm a brand name", "domain availability".

SKILL.md

3.5 KB, as published. Nobody here has run it

Domain Search

Brainstorm brandable names and check which domains are actually available to register.

How availability is checked: RDAP (not WHOIS, not a paid API)

Availability is determined with RDAP — the official IETF successor to WHOIS (RFC 9082/9083). Query https://rdap.org/domain/<fqdn>, which routes to the responsible registry and returns:

HTTP 404 → AVAILABLE (no registration record exists)
HTTP 200 → TAKEN (a registration record exists)
anything else → UNKNOWN (TLD has no RDAP server, rate-limited, or network issue)

This is authoritative and free. It is more reliable than scraping Instant Domain Search / GoDaddy, whose public endpoints change and rate-limit. RDAP tells you registered or not; it does not price premium/reserved names — confirm the final price at a registrar.

Caveats (state these when relevant)

Not all TLDs publish RDAP. .io historically had no RDAP, and some ccTLDs still don't. UNKNOWN means "couldn't determine" — never report it as available.
.com, .ai, .net, .org, .app, .dev, .co work well via RDAP.
An RDAP-available name can still be a premium listing (high price). Verify at checkout.

The script

scripts/check-domains.sh — batch checker. Always pass it as an explicit list (zsh does not word-split unquoted variables, so loop over arrays or pass args directly).

# Names × TLDs (cartesian):
bash scripts/check-domains.sh --tlds com,ai,app myname otherword

# Explicit FQDNs:
bash scripts/check-domains.sh acme.com acme.ai foo.io

# Machine-readable (for further processing):
bash scripts/check-domains.sh --json --tlds com,ai myname

Output uses ✅ AVAILABLE / ❌ taken / ❓ unknown.

Workflow

Understand the product before brainstorming. Check the repo, README, and (if present) the user's memory/notes so names fit the actual positioning, audience, and tone.
Brainstorm in styles, not at random — mix: real words, invented/portmanteau, foreign words, compounds, and verb+suffix (-ly, -ify, -ish). Short single words are almost always taken on .com; compounds and coined words are where .com wins are found.
Batch-check with the script across the TLDs the user cares about (default .com,.ai).
Present results grouped by availability, leading with names available on the user's preferred TLD. For each, give a one-line rationale (what it evokes) so the choice is informed.
Remind that RDAP-available ≠ final price; premium names cost more — verify at a registrar (Cloudflare Registrar is at-cost and a good default if the user already uses Cloudflare).

Tips

Default to checking .com and .ai; add .app/.io/.dev for developer-facing tools.
If the user already owns domains (e.g. registered at Cloudflare), check whether one fits before suggesting new purchases — reusing an owned domain is free.
Avoid names colliding with direct competitors or trademarks; flag near-misses you notice.