Attach popular brand prefixes/suffixes to a seed word and check each `.com` via Verisign RDAP. Use when the user names a word and asks for prefix/suffix `.com` variants, or wants domains generated by adding endings like -ly/-ify/-hub or beginnings like open-/get-/go-.
Installation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Attach popular brand prefixes/suffixes to a seed word and check each `.com` via Verisign RDAP. Use when the user names a word and asks for prefix/suffix `.com` variants, or wants domains generated by adding endings like -ly/-ify/-hub or beginnings like open-/get-/go-.
affix-domains
Affix a seed word with common brand prefixes and suffixes, check each .com live, and prompt the user to register the free ones.
Steps
Generate candidates. For seed W, produce W + each suffix and each prefix + W from the catalog below. Lowercase. Dedupe. Drop any combination that spells an existing English word (e.g. getup, openbox) — its .com is almost certainly taken and burns an RDAP call. If the user hints a style (playful, techy, marketplace…), weight the matching categories; default is every category.
Check .com availability via Verisign RDAP (authoritative for .com):
for d in cand1.com cand2.com ...; do
code=$(curl -s -o /dev/null -w "%{http_code}" --max-time 10 \
"https://rdap.verisign.com/com/v1/domain/${d}")
# 404 = AVAILABLE, 200 = TAKENdone
For >15 candidates parallelize with xargs -P 8. Treat only 404 as available; anything else means taken or ambiguous.
Surface the survivors grouped by the catalog category that produced them. One line per free .com.
Prompt the user to register. Ask which they want to take. Point them to Cloudflare Registrar (or their preferred one). Do not enter payment on their behalf — registration is the user's action.
