domain
When you want to brainstorm and check available .com domains for a new project — brand naming, aftermarket pricing (HugeDomains / Afternic / Sedo / Dan), USPTO trademark screening, and social handle availability. Built on Laura Roeder's \"work backwards from availability, not from a name you fell in love with\" methodology. Uses Vercel CLI + whois + Domainr API + Namecheap API + agent-browser for the pieces each tool actually reliably supports (multi-tool ensemble because no single tool covers everything cleanly). 11-step workflow: budget → brainstorm → primary availability check → whois cross
npx skills add coreyhaines31/makerskills --skill domain --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /domain — Brainstorm + check available .com domains Multi-tool workflow to find a great, affordable, available .com for a new project. Built on Laura Roeder's rule: **work backwards from what's actually available — don't fall in love with a name first** ([source](https://lauraroeder.com/how-i-nabbed-the-com-for-my-bootstrapped-startup-without-spending-a-million-bucks-6dc35c4606e9)). Defaults to `.com` only. Only deviate (.dev, .co, .io, .ai) if the project is dev-tooling-only or the user explicitly asks. ## Step 0 — Environment checks Verify these before proceeding (surface install commands if missing, don't try to install silently): | Tool | Check | Install if missing | |---|---|---| | Vercel CLI | `vercel whoami` | `npm i -g vercel && vercel login` | | whois | `which whois` | `brew install whois` (macOS) | | Domainr API key | `[ -n "$DOMAINR_API_KEY" ]` | Get free key at rapidapi.com/domainr/api/domainr, add to `~/.zshenv` | | Namecheap API | `[ -n "$NAMECHEAP_API_KEY" ] && [ -n "$NAMECHEAP_API_USER" ] && [ -n "$NAMECHEAP_CLIENT_IP" ]` | Enable API at ap.www.namecheap.com/settings/tools/apiaccess/, add 3 env vars, whitelist your IP | Domainr + Namecheap are optional — the workf
- Step 0 — Environment checks
- Step 1 — Set the budget
- Step 2 — Seed words for "branded" combos
- Step 3 — Primary availability check (Vercel CLI)
- Step 4 — Cross-check with whois
- Step 5 — Domainr cross-check (aftermarket signal)
- Step 6 — Namecheap price check
- Step 7 — Aftermarket sweep for taken candidates
- Step 8 — Bucket the results
- Step 9 — Negotiate on aftermarket listings
- Step 10 — NOW do the name research (not before!)
- Step 10a — USPTO trademark search via agent-browser
- Step 10b — Social handle availability
- Step 11 — Buy it
for domain in candidate1.com candidate2.com candidate3.com; do echo -n "$domain: " vercel domains check "$domain" 2>&1 | grep -E "available|not available|Error" || echo "checking..." done vercel domains price candidate1.com candidate2.com candidate3.com vercel domains inspect candidate.com for domain in candidate1.com candidate2.com; do echo "$domain → $status" for domain in candidate.ai; do if echo "$result" | grep -qi "no object found\|no match\|not registered\|no entries found"; then
What does the domain skill do?
When you want to brainstorm and check available .com domains for a new project — brand naming, aftermarket pricing (HugeDomains / Afternic / Sedo / Dan), USPTO trademark screening, and social handle availability. Built on Laura Roeder's \"work backwards from availability, not from a name you fell in love with\" methodology. Uses Vercel CLI + whois + Domainr API + Namecheap API + agent-browser for the pieces each tool actually reliably supports (multi-tool ensemble because no single tool covers everything cleanly). 11-step workflow: budget → brainstorm → primary availability check → whois cross
How do I install it?
Run `npx skills add coreyhaines31/makerskills --skill domain --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From coreyhaines31/makerskills, a repository with 500 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
