Individual skill
domain-name
Use this skill when the founder needs to name a product or company and find a domain: 'name my product,' 'what should I call it,' 'help me pick a domain,' 'is this a good name,' 'my domain is taken,' 'check if this name is available,' or a pasted list of candidate names. Scores names against ten rules, then checks domain availability with DNS and RDAP. Not for pointing DNS at a host once the name is chosen (use go-live) or for writing page copy (use landing-page).
skills/domain-name/SKILL.md
Source commit 01bd10f79a4b6a741be78e3184612a90ecbd54ef
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 262
- Repository last updated
- Oct 16, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,097 bytesSKILL.mdcore · 10,097 bytesreferences/scorecard.mddoc · 15,374 bytesscripts/check-availability.pyruns · 6,113 bytes
Read excerpt
# Naming a product and getting the domain
A name can fail in two ways: it is a bad name, or it is a good name you cannot have. Judge the concept first. Test availability second.
## Optimize in this order
```
great concept → great name → acceptable domain
```
**Never the reverse.** The failure is subtle: one pattern starts returning free domains, so you generate more of that pattern, and within two rounds availability is choosing the concept. The symptom is a list where most names share a word or a shape.
A great name with an acceptable domain beats a mediocre name with a perfect one. `Foothold` on `getfoothold.com` works. `socialengagementautomation.com` is still a dead name. When a strong name's exact domain is gone, try other suffixes in the acceptable set and the `get`/`use` + one word wrapper (rules 7 and 10 in the scorecard) before dropping the name. Drop a name for being weak, never for being taken.