Research
OutThisLife/brooklyn-skills
Look it up before answering or building — this project's documents of record first, then external prior art.
Run candidate product, brand, company, or benchmark names through an audition — authoritative domain-availability checks, collision research across SaaS/GitHub/packages/the target adjacent domain, a…
Install Name Audition
$ npx skills add glebis/claude-skills --skill name-audition -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install glebis/claude-skills name-audition --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/name-audition .claude/skills/name-audition && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "name-audition" agent skill from https://github.com/glebis/claude-skills/tree/main/name-audition into .claude/skills/name-audition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "name-audition", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/glebis/claude-skills/tree/main/name-auditionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add glebis/claude-skills --skill name-audition -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install glebis/claude-skills name-audition --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/name-audition .agents/skills/name-audition && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "name-audition" agent skill from https://github.com/glebis/claude-skills/tree/main/name-audition into .agents/skills/name-audition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "name-audition", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add glebis/claude-skills --skill name-audition -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install glebis/claude-skills name-audition --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/name-audition .cursor/skills/name-audition && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "name-audition" agent skill from https://github.com/glebis/claude-skills/tree/main/name-audition into .cursor/skills/name-audition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "name-audition", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/glebis/claude-skills.git --path name-audition--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add glebis/claude-skills --skill name-audition -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install glebis/claude-skills name-audition --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/name-audition .gemini/skills/name-audition && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "name-audition" agent skill from https://github.com/glebis/claude-skills/tree/main/name-audition into .gemini/skills/name-audition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "name-audition", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install glebis/claude-skills name-auditionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add glebis/claude-skills --skill name-audition -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/name-audition .github/skills/name-audition && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "name-audition" agent skill from https://github.com/glebis/claude-skills/tree/main/name-audition into .github/skills/name-audition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "name-audition", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add glebis/claude-skills --skill name-audition -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install glebis/claude-skills name-audition --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/name-audition .opencode/skills/name-audition && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "name-audition" agent skill from https://github.com/glebis/claude-skills/tree/main/name-audition into .opencode/skills/name-audition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "name-audition", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
name-audition- GitHub stars
- 391
- Token cost
- ~2.1k tokens
- SKILL.md length
- 1,021 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 92
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run candidate product, brand, company, or benchmark names through an audition — authoritative domain-availability checks, collision research across SaaS/GitHub/packages/the target adjacent domain, a…
- Works in 3 steps: Adjacent-domain collision is the worst… → Descriptive / generic names are… → Search visibility ≠ availability. "I…
- The user is naming a product
- SKILL.md covers The core lesson this skill…, Workflow — the casting call, Stage 3b — collision research… and Decision rules, plus 5 more sections
- Runs Shell scripts from its folder; calls apt
What it does
Name Audition is an agent skill from glebis/claude-skills. Run candidate product, brand, company, or benchmark names through an audition — authoritative domain-availability checks, collision research across SaaS/GitHub/packages/the target adjacent domain, a light trademark and ownability read, a ranked callback list, and an interactive casting report of finalists with optional draft branding. Use when the user is naming a product, app, company, feature, or benchmark; asks "is this name taken", "check these domains", "help me pick a name", "is X available", "name my…
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/check_domains.sh`).
It sits in Legal & Compliance, covering Intellectual property. It works with GitHub. The repository describes itself as: Collection of Claude Code skills for enhanced AI workflows. The licence is MIT.
When your agent uses it
- The user is naming a product
- Asks is this name taken
- Check these domains
- Help me pick a name
Example prompts
- “is this name taken”
- “check these domains”
- “help me pick a name”
- “/name-audition”
Requirements
- A Bash shell
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Adjacent-domain collision is the worst kind. A product already operating in the target
- Descriptive / generic names are domain-free but weak. Easy to register, hard to own — bad
- Search visibility ≠ availability. "I didn't see it in results" is not proof a name is
What it can do on your machine
Read from SKILL.md and the folder at commit 3b88261. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
apt
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Name Audition loads about 2.1k tokens when it runs. Until then it costs about 166 tokens; SKILL.md has 1,021 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from glebis/claude-skills at commit 3b88261, republished under its MIT licence (© glebis). 1,021 words, ~2,085 tokens.
Download SKILL.mdSave it as
.claude/skills/name-audition/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- name-audition
- description
- Run candidate product, brand, company, or benchmark names through an audition — authoritative domain-availability checks, collision research across SaaS/GitHub/packages/the target adjacent domain, a light trademark and ownability read, a ranked callback list, and an interactive casting report of finalists with optional draft branding. Use when the user is naming a product, app, company, feature, or benchmark; asks "is this name taken", "check these domains", "help me pick a name", "is X available", "name my product", "brand name research", "audition names"; or wants to compare and pressure-test a shortlist of candidate names before committing.
Name Audition — «Кастинг имён»
Audition candidate names before you cast one. Brandability is not availability, and a free domain is not a safe name — the audition separates the three. Candidates try out; the best one gets cast; the rest simply don't make the cut.
The core lesson this skill encodes
A name can sound perfect, score well, have every domain free — and still be the wrong choice. Three ways a candidate fails its screen test, worst first:
- Adjacent-domain collision is the worst kind. A product already operating in the target vertical means a name doesn't make the cut even when the string is free to register — confusion and SEO dilution are fatal in the same space.
- Descriptive / generic names are domain-free but weak. Easy to register, hard to own — bad for trademark, bad for SEO, easy for competitors to crowd.
- Search visibility ≠ availability. "I didn't see it in results" is not proof a name is free. Verify with authoritative sources before casting.
Workflow — the casting call
Run these stages in order. Stages 3a and 3b run together.
- Brief. Establish: (a) what is being named (product / app / company / feature / benchmark),
(b) scope + one-line description, (c) the adjacent domain — the vertical it lives in
(healthcare, coaching, privacy/security, dev tooling); the user supplies this, (d) tone / vibe,
(e) which TLDs matter (default
.com .org .ai .io .app .co). If (a)–(c) is missing, ask first — the adjacent domain is what makes collision research meaningful. - The audition. Generate 4–8 candidate names matching the tone. Favor short, pronounceable, ownable coinages over descriptive compounds. Note for each what it means / why it fits.
- The screen test (run 3a and 3b together):
- 3a — Domains (authoritative). Run
scripts/check_domains.sh NAME [NAME ...] -- com ai io ...for a name × TLD availability table. WHOIS no-match + no NS = registrable; Creation Date / Registrar / NS present = taken; ambiguous = verify by hand. Authoritative for registration, never for trademark. - 3b — Collision research. For each candidate, use the
firecrawlskill or web search (never beautifulsoup) to check the sources below.
- 3a — Domains (authoritative). Run
- Callbacks. Build a per-candidate risk table and rank by safety + ownability.
- Casting report. Use the
presentskill to build an interactive HTML deck — one slide per finalist plus a ranked comparison and a "cast it?" slide. - Branding (optional, gated). Only if the user wants it: draft a wordmark/logo per finalist
with
nano-bananaorgpt-image-2(draft quality), embed in the slides. - Cast → user decides. Give a clear top pick with reasoning; the user makes the final call. Names that fail "didn't make the cut" — never "killed".
Stage 3b — collision research checklist
For each candidate, search these surfaces and record URLs:
- SaaS / AI / startups — Crunchbase, Product Hunt, a plain web search of
"<name>"+ vertical. - Code namespace — GitHub repos literally named it; PyPI and npm packages with that exact name.
- The adjacent domain (most important) —
"<name>"+ the user's vertical. A same-vertical hit is the one that ends an audition. - Privacy / security tooling — relevant if the thing touches data handling.
- Trademark + ownability — a light USPTO / EUIPO look for live marks in the relevant classes, plus a judgment call on descriptiveness: distinctive enough to own, or a generic compound a competitor can crowd?
- Benchmark names — if naming a benchmark, the decisive check is the literature, not domains: is the name already a published dataset/benchmark (arXiv / ACL / Papers with Code)? Citation clash, not a domain, is what matters there.
Output table:
| Name | Notable existing uses (URLs) | Adjacent-domain clash? | Trademark / ownability | Verdict |
|---|---|---|---|---|
| Acme | github.com/x, acme.io (logistics) | No | Distinctive, no live marks | Callback |
Verdict is Callback (advances) / Cut (out) / Cast (the pick). Apply the Decision rules.
Show full SKILL.md (422 more words)Show less
Decision rules
- Adjacent-domain collision → Cut. Even if every domain is free. A competing product in the same vertical poisons the name.
- Descriptive / generic compound → weak. Domains may be free, but hard to trademark and bad for SEO. Flag the ownability risk even when registrable.
- Domains-free ≠ safe. Availability is necessary, not sufficient. A name earns the part only when it is both registrable and clear of adjacent-domain and trademark collisions.
- Verify before casting. Confirm domains with
check_domains.shand trademark with a registry lookup, not with "I didn't find anything." - Rank by safety first, then ownability, then aesthetics.
Example (a real audition)
Naming a privacy-focused de-id toolkit + benchmark for the mental-health / coaching vertical. Audition: Praxio, Dyad, Sessio, ClientPII, CONFIDE.
| Name | Screen test | Verdict |
|---|---|---|
| Praxio | Sounded great, but Praxis EMR is a mental-health EHR — adjacent-domain collision in the exact vertical. | Cut |
| Dyad | Clean, meaningful, but dyad.sh is a local-AI dev tool and dyad.ai is a healthcare company — collisions in both tech and the vertical. | Cut |
| Sessio | Nice, but sessio.base44.app is a same-vertical product for therapists. | Cut |
| ClientPII | All TLDs free — but a generic descriptive compound, weak to trademark, bad SEO. | Didn't make the cut (as a brand) |
| CONFIDE | Domains all taken (bad product brand) — but as a benchmark name, citation-collision is low. | Cast (as the benchmark name) |
One line: domains-free ≠ safe, and brandable ≠ available. Most names that look good fail on adjacent-domain collisions a domain check alone would never catch.
scripts/check_domains.sh
scripts/check_domains.sh praxio dyad sessio # default TLDs (.com .org .ai .io .app .co)
scripts/check_domains.sh praxio dyad -- com ai io # custom TLDs after a --
TLDS="com org ai" scripts/check_domains.sh praxio # or via envPer domain it runs whois (following the IANA registry referral when needed) plus dig +short NS,
printing a name × TLD table of free / taken / ?. ? = verify by hand (WHOIS rate-limit or
.ai flakiness). Needs whois and dig on PATH (ship with macOS; apt install whois dnsutils).
Referenced skills
firecrawl— collision / literature research (stage 3b). Never beautifulsoup.present— interactive HTML casting report (stage 5). Pass it the comparison + per-name slides.nano-bananaorgpt-image-2— optional draft branding (stage 6). Draft quality by default.
Safety & limits
- WHOIS is authoritative for registration, not trademark. A free domain can still infringe a live mark. Always do the separate trademark read.
.aiWHOIS is flaky. Treat?as "check the registrar's search," not "free."- The script proves registrability, not legal clearance — no trademarks, social handles, or app-store conflicts. For a name you'll build a business on, get an attorney's clearance.
- Branding is optional and gated — generate logos only when the user asks; draft quality unless told otherwise.
- The user casts. The skill recommends; it does not commit.
Install
Portable across Claude Code and Codex — plain-prose workflow, one bash script, no Claude-only tools.
cp -R name-audition ~/.claude/skills/ # Claude Code
cp -R name-audition ~/.agents/skills/ # Codex© glebis, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (scripts) in name-audition of glebis/claude-skills.
- SKILL.md
- scripts/check_domains.sh
Open the folder on GitHubat commit 3b88261
Compare with similar skills
Name Audition next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Name Audition this skillglebis/claude-skills | 391 | — | ~2.1k | Automated safety check: Pass | MIT | |
| ResearchOutThisLife/brooklyn-skills | 199 | — | ~978 | Automated safety check: Pass | MIT | |
| Prior Art Scoutn1m21n/Infinite | 271 | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Weak Signal SynthesizerOneWave-AI/claude-skills | 336 | 1 repos | ~500 | Automated safety check: Pass | MIT | |
| Open-Source Release Readinesstrailofbits/skills | 7.5k | — | ~2.6k | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Search Contextinstructa/agent-skills | 139 | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Prior Art Scout
n1m21n/Infinite
Find publicly documented solutions (peer repos, GitHub, forums) to bugs, platform quirks, dependency gotchas or architectural patterns, respecting the copyleft discussions-only rule.
Weak Signal Synthesizer
OneWave-AI/claude-skills
Identify EMERGING trends by connecting dots across unrelated sources.
- Official
Open-Source Release Readiness
trailofbits/skills
Walks a repository through release readiness before it goes public: secrets audit, licensing, documentation, CI and language-specific packaging.
Search Context
instructa/agent-skills
Find, clone, inspect, and summarize high-quality GitHub reference repositories for coding agents.
Mechanical Engineering Research
ccplugins/awesome-claude-code-plugins
Research, write, code, analyze, present, and develop proposals for thermal-fluid mechanical engineering work with source-aware rigor.
More from glebis/claude-skills
All 92 skills in this repoPII Annotation and Agreement Scorer
glebis/claude-skills
Runs a human-first workflow for labeling PII spans in a transcript, then scores inter-annotator agreement and drafts an adjudicated gold set.
Non-Destructive Chrome Automation
glebis/claude-skills
Automates a dedicated, logged-in Chrome instance per profile without ever closing the user's own open tabs or browser windows.
Deep Research
glebis/claude-skills
This skill should be used when conducting comprehensive research on any topic using the OpenAI Deep Research API.
Elimination Research
glebis/claude-skills
This skill should be used for elimination-style research where the user wants to choose from a shortlist of products, tools, services, vendors, or other options using explicit criteria, numeric…
Narrated HTML Presentations
glebis/claude-skills
Generates a self-contained HTML presentation with article and slides modes, ElevenLabs voiceover narration and optional GPT Image 2 illustrations.
Synthetic Coaching Session Generator
glebis/claude-skills
Writes fictional but realistic coaching or therapy session transcripts for evals, demos and few-shot examples, in several modalities and export formats.
Related
Works with
Categories
Questions about Name Audition
What does Name Audition do?
Run candidate product, brand, company, or benchmark names through an audition — authoritative domain-availability checks, collision research across SaaS/GitHub/packages/the target adjacent domain, a…. Name Audition is an agent skill from glebis/claude-skills. Run candidate product, brand, company, or benchmark names through an audition — authoritative domain-availability checks, collision research across SaaS/GitHub/packages/the target adjacent domain, a light trademark and ownability read, a ranked callback list, and an interactive casting report of finalists with optional draft branding.
When should I use Name Audition?
Name Audition fits situations like: the user is naming a product; asks is this name taken; check these domains; help me pick a name.
How do I install Name Audition in Claude Code?
Run `npx skills add glebis/claude-skills --skill name-audition -a claude-code`. Or copy the skill folder (name-audition in glebis/claude-skills) into .claude/skills/name-audition in your project. Claude Code loads it when a task matches its description.
How do I install Name Audition in Codex?
Run `npx skills add glebis/claude-skills --skill name-audition -a codex`. Or copy the skill folder (name-audition in glebis/claude-skills) into .agents/skills/name-audition in your project. Codex loads it when a task matches its description.
Can I use Name Audition in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add glebis/claude-skills --skill name-audition -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/name-audition, .gemini/skills/name-audition, .github/skills/name-audition and .opencode/skills/name-audition in your project.
What does Name Audition need to run?
Going by SKILL.md and its folder, Name Audition needs a shell for the scripts in its folder and the command-line tools its instructions call (apt). Our summary lists: A Bash shell.
Does Name Audition access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Name Audition safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Name Audition use?
Name Audition is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Name Audition use?
About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Name Audition?
Skills that share tags, products or a category with Name Audition: Research (OutThisLife/brooklyn-skills, 199 stars), Prior Art Scout (n1m21n/Infinite, 271 stars), Weak Signal Synthesizer (OneWave-AI/claude-skills, 336 stars) and Open-Source Release Readiness (trailofbits/skills, 7.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Name Audition?
glebis (a GitHub user) maintains it in glebis/claude-skills, which has 391 GitHub stars. The repository holds 92 skills in this directory. The repository was last updated on October 8, 2026.
Source: glebis/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.