Find a domain with the Namegarage catalog skill

Releases#agents#search#domains#clawhub#skills-sh

The Namegarage catalog skill is now available on ClawHub and skills.sh. It gives your assistant instructions for finding domains in our catalog and checking their current prices. No Namegarage account or API key is needed.

Install the skill

For OpenClaw, install version 1.0.0 from ClawHub:

openclaw skills install @namegarage/catalog --version 1.0.0

For Codex, Claude Code, Cursor, or another agent supported by the skills CLI:

npx skills@1.7.4 add https://github.com/namegarage/skills/tree/v1.0.0 --skill catalog

The skills CLI lets you choose the agent and workspace. Both directories distribute the same public catalog instructions. You can inspect the source on GitHub or the ClawHub security audit before installing.

Describe the project and budget

Try a prompt like this:

Use the Namegarage catalog skill to find up to five domains for a meal-planning app under $3,000 USD. Show current prices and listing links, and explain why each name fits.

Search accepts a project description or keywords. You can narrow results by budget, domain suffix, length, or tier. Use general descriptions rather than confidential project details: your search text is sent to Namegarage.

Results come from Namegarage's public catalog. A missing price means the name is offer-only. A name missing from the catalog may still be registered or listed elsewhere. Follow a result's link to review its current price and purchase options; a search does not reserve the domain.

The skill uses our public read interfaces. It cannot buy a domain, make an offer, send a message, or access private portfolio records.

For other assistants, use our MCP connection guide or the public API quickstart. You can also browse the catalog yourself.

X LinkedIn Email

Comments

Comments are reviewed before publication. The Author badge marks replies from the author.

Read approved comments on the discussion page.

    Open the discussion page

    Leave a comment

    Your account name, sign-in provider, and comment become public after review. Your email stays private. See the blog comments privacy notice and Privacy Policy.

    Sign in to leave a comment.