About letsfinddomain-skill
A domain-naming skill that helps users develop candidates, check availability through a configured provider, and review pricing and potential brand conflicts. It is read-only and does not purchase or change domains or DNS.
Key features
- 01Clarifies product and naming requirements
- 02Generates domain candidates
- 03Checks availability with a configured provider
- 04Shows first-year and renewal pricing
- 05Flags potential brand collisions
Use cases
- 01Finding domain names for a product brief
- 02Checking candidates against budget and TLD preferences
- 03Reviewing available names for pricing and brand conflicts
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/letsfinddomain-skillin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
README.zh-CN.mdLICENSEAGENTS.md.env.example.gitignoreREADME.md.githooks/pre-commitagents/openai.yamldocs/providers/cloudflare/setup.mdsetup.zh-CN.mddocs/providers/dynadot/setup.zh-CN.mdsetup.mddocs/providers/godaddy/setup.mdsetup.zh-CN.mddocs/providers/namecheap/setup.mdsetup.zh-CN.mddocs/providers/namecom/setup.zh-CN.mdsetup.mddocs/providers/namesilo/setup.zh-CN.mdsetup.mddocs/providers/porkbun/setup.mdsetup.zh-CN.mddocs/providers/spaceship/setup.mdsetup.zh-CN.mdinstall/letsfinddomain-skill.mdcagents-snippet.mdreferences/naming-guide.mdrate-limits.mdproviders.mdquery-recipes.mdDetails
From the project READMELet'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.compreflight 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
.envis 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.
availablemust 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.mdwhen 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.mdonly 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, andnot 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.
Comments
Markdown supported