Let's Find Domain
Help the user find a strong domain name, confirm its availability, show first-
year and renewal pricing, and flag obvious brand collisions.
User-first behavior
- Start with the user's request. Do not run a standalone
example.com
preflight before understanding what they want.
- Use the bundled scripts internally. In normal user-facing replies, do not
show Python commands or ask users to assemble command-line arguments.
- Use system environment variables first; a repository
.env is a local
fallback. Spaceship is the default availability provider when configured.
- If no availability provider is configured, say so in one or two sentences and
link to
references/environment.md. Do not dump
every provider, RDAP caveat, or setup command unless the user asks.
- Never guess availability.
available must come from a real provider; an
unresolved result is not available.
Workflow
- Understand the brief: product, audience, naming style, length, TLDs, budget,
banned or required words, and existing candidates. Ask only for missing
information that changes the search.
- Generate candidates around the brief. Use
references/naming-guide.md when useful, but
treat it as a palette rather than a whitelist.
- When availability is requested, send the complete candidate list in one
batch. Respect the selected provider's batch shape, shared rate budget, and
one in-flight request rule; see
references/rate-limits.md
only when needed.
- Vet available names for established brand or product collisions. Surface
premium pricing and large renewal increases instead of hiding them.
- Present a compact table with domain, status, registration price, renewal
price, and notes. Recommend the strongest option when the user asks for
suggestions, not just a raw list.
Failure handling
- No provider: explain that availability cannot be confirmed yet and point to
the cross-platform setup in
references/environment.md.
lookup failed, unknown, no RDAP for this TLD, and not supported by this provider: report as unresolved, never as available.- RDAP is only an optional trial fallback. It reports registration records, not
guaranteed purchasability or checkout pricing.
Scope
Read-only only. Never buy, transfer, or modify domains or DNS. The user makes
the purchase in their registrar account.
1---2name: letsfinddomain-skill3description: Generate, check, and vet domain names. Use when the user wants domain name ideas, wants to check whether domains are available, or wants to compare registration and renewal prices across TLDs.4---56# Let's Find Domain78Help the user find a strong domain name, confirm its availability, show first-9year and renewal pricing, and flag obvious brand collisions.1011## User-first behavior1213- Start with the user's request. Do **not** run a standalone `example.com`14 preflight before understanding what they want.15- Use the bundled scripts internally. In normal user-facing replies, do not16 show Python commands or ask users to assemble command-line arguments.17- Use system environment variables first; a repository `.env` is a local18 fallback. Spaceship is the default availability provider when configured.19- If no availability provider is configured, say so in one or two sentences and20 link to [`references/environment.md`](references/environment.md). Do not dump21 every provider, RDAP caveat, or setup command unless the user asks.22- Never guess availability. `available` must come from a real provider; an23 unresolved result is not available.2425## Workflow26271. Understand the brief: product, audience, naming style, length, TLDs, budget,28 banned or required words, and existing candidates. Ask only for missing29 information that changes the search.302. Generate candidates around the brief. Use31 [`references/naming-guide.md`](references/naming-guide.md) when useful, but32 treat it as a palette rather than a whitelist.333. When availability is requested, send the complete candidate list in one34 batch. Respect the selected provider's batch shape, shared rate budget, and35 one in-flight request rule; see [`references/rate-limits.md`](references/rate-limits.md)36 only when needed.374. Vet available names for established brand or product collisions. Surface38 premium pricing and large renewal increases instead of hiding them.395. Present a compact table with domain, status, registration price, renewal40 price, and notes. Recommend the strongest option when the user asks for41 suggestions, not just a raw list.4243## Failure handling4445- No provider: explain that availability cannot be confirmed yet and point to46 the cross-platform setup in [`references/environment.md`](references/environment.md).47- `lookup failed`, `unknown`, `no RDAP for this TLD`, and `not supported by this48 provider`: report as unresolved, never as available.49- RDAP is only an optional trial fallback. It reports registration records, not50 guaranteed purchasability or checkout pricing.5152## Scope5354Read-only only. Never buy, transfer, or modify domains or DNS. The user makes55the purchase in their registrar account.
meepo-it