domain-search
Skill2 starsChanged 15 days agoMITView on GitHub
Use when checking whether domain names are available to register or what registering them costs.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Put every name of the request into one run.
- Very specific: line 25
When the user names no TLDs, omit --tlds: the default set is the user's usual com, ai, app, io and dev.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.
Files
Domain search
Answer with scripts/search-domains.py from this skill's directory. A domain
with a DNS delegation counts as taken; for the rest, the TLD's registry gives
the verdict over RDAP, then WHOIS. Each result carries Porkbun's list price and
the TLD's popularity rank. The script needs python3, dig and network
access; when it exits with an error, report that message as the blocker.
Run the search
Put every name of the request into one run. A bare label (acme) is tried
across the TLDs; a full domain (acme.io) is checked as given.
python3 <skill-dir>/scripts/search-domains.py acme acmehq
python3 <skill-dir>/scripts/search-domains.py acme --tlds com,co,xyz
python3 <skill-dir>/scripts/search-domains.py acme --all- When the user names no TLDs, omit
--tlds: the default set is the user's usual com, ai, app, io and dev. Named TLDs replace it. - A request for all TLDs or every extension takes
--all. Raise--limit(30 registry checks per name) only as far as the user asks for more confirmed results.
The script replaces tldx here, and one run per request keeps its pacing intact. Registries throttle bulk lookups per IP address: a 660-TLD tldx burst drew a 24-hour RDAP block from Identity Digital, which serves over 400 TLDs including .ai and .info, and tldx then reported throttled lookups such as google.live as available.
Report the results
Present the results for each name in the user's language as bullet points, one domain per bullet with its status and price, as the script prints them. Every check the user asks for gets the prices, even when they ask only about availability. With these statuses:
- available: the registry has no record of the domain. Reserved and premium names have no record either, so the registrar's checkout confirms that it can be registered and at what price.
- taken: the registry or DNS shows a registration.
- unconfirmed: DNS has no delegation, but the registry check failed or was throttled. Report that availability is not confirmed, with the reason, apart from the confirmed results: a registered domain can lack DNS. An unconfirmed .cl or .es gets a link to https://www.nic.cl or https://www.dominios.es: neither registry offers RDAP, and their WHOIS servers did not answer this machine.
- unknown: DNS gave no clear answer, because it failed or the TLD has wildcard DNS, and the registry check failed too.
Point out a renewal well above the first-year price. To compare registrars for
a shortlisted TLD, link https://tld-list.com/tld/<tld>. When you recommend a
ccTLD, mention that it may restrict who can register it, as .us, .eu and .ca do.
For --all, also give the number of TLDs checked, the counts of taken TLDs and
of TLDs not checked with the registry per name, and the most popular of the
unchecked ones with their prices, marked as not confirmed. Its universe is
every DNS-root TLD that Porkbun prices, plus .cl and .es; another TLD, such as
.fr, is checked only when named with --tlds.
Done when each requested name has its bullets, every bullet carries its price or the script's tld-list.com link, every unconfirmed or unknown domain is reported with its reason, and each warning line from the script is relayed.
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- headlessdomains/skills★ 1same name
- thattimc/skills★ 1same name
- bluei98/claudecode-skill-domain-search★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository48 other files it gives its agents.
- accessibilitySkill
- agent-instructionsSkill
- analyze-change-effectsSkill
- article-processingSkill
- ci-cd-automationSkill
- comment-styleSkill
- commitSkill
- communicate-clearlySkill
- compare-solutionsSkill
- create-project-instructionsSkill
- daily-meeting-updateSkill
- debugSkill
- deprecate-and-removeSkill
- design-code-structureSkill
- error-handlingSkill
- explain-codeSkill
- explain-decisionsSkill
- github-actionsSkill
- handoffSkill
- humanizeSkill
- issue-workflowSkill
- observabilitySkill
- people-memorySkill
- performance-optimizationSkill
- planningSkill
- pr-followupSkill
- prototypeSkill
- pr-review-followupSkill
- pr-reviewSkill
- prSkill
- report-work-activitySkill
- retroSkill
- review-code-changesSkill
- simplify-codeSkill
- skill-maintenanceSkill
- stacked-prSkill
- task-breakdownSkill
- tddSkill
- teachSkill
- typescript-best-practicesSkill
- verification-authoringSkill
- verifySkill
- wayfinderSkill
- workflow-to-skillSkill
- work-modeSkill
- worktrunkSkill
- write-documentationSkill
- youtube-processingSkill
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
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.

