name-audition

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

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.

一个名字可能听起来完美、评分很高、所有域名都可用——但仍可能是错误选择。候选名称未通过筛选测试的三种情况，按严重程度排序：

相邻领域冲突是最严重的问题。若目标垂直领域内已有同类产品使用该名称，即便字符串可注册，这个名字也会被淘汰——同一领域内的混淆和SEO稀释是致命的。
描述性/通用名称虽域名免费但竞争力弱。注册容易，但难以拥有——不利于商标注册、SEO表现差，易被竞争对手挤占。
搜索可见性≠可用性。“我在搜索结果里没找到”不能证明名称可用。确定前务必通过权威来源验证。

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
```
firecrawl
```
  skill or web search (never beautifulsoup) to check the sources below.
Callbacks. Build a per-candidate risk table and rank by safety + ownability.
Casting report. Use the
```
present
```
skill 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-banana
```
or
```
gpt-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".

按顺序执行以下阶段。阶段3a和3b同步进行。

需求确认：明确：(a) 命名对象（产品/应用/公司/功能/基准），(b) 范围及一句话描述，(c) 相邻领域——所属垂直领域（医疗健康、教练服务、隐私/安全、开发工具等）；由用户提供，(d) 风格/氛围，(e) 重要的TLD（默认
```
.com .org .ai .io .app .co
```
）。若(a)-(c)缺失，先向用户询问——相邻领域是冲突调研的核心依据。
生成候选名称：生成4-8个符合风格的候选名称。优先选择简短、易读、可专属化的自创词，而非描述性复合词。为每个名称标注含义及适配理由。
筛选测试（同步执行3a和3b）：
- 3a — 权威域名检查：运行
```
scripts/check_domains.sh NAME [NAME ...] -- com ai io ...
```
  生成名称×TLD可用性表格。WHOIS无匹配+无NS记录=可注册；存在创建日期/注册商/NS记录=已被占用；结果模糊=手动验证。此方法仅对注册可用性权威，对商标无效。
- 3b — 冲突调研：为每个候选名称使用
```
firecrawl
```
  技能或网页搜索（禁止使用beautifulsoup）检查以下来源。
候选名单筛选：为每个候选名称构建风险表，并按安全性+可拥有性排序。
选拔报告：使用
```
present
```
技能生成交互式HTML演示文稿——每个最终候选名称对应一页幻灯片，加上排名对比页和“是否选中”页。
品牌设计（可选，需用户触发）：仅当用户要求时，使用
```
nano-banana
```
或
```
gpt-image-2
```
为每个最终候选名称生成草稿字标/ logo（草稿质量），并嵌入幻灯片。
最终决策→用户确认：给出明确的首选名称及理由；最终由用户决定。未通过审核的名称表述为“未入选”——绝对不能用“淘汰”。

Stage 3b — collision research checklist

阶段3b — 冲突调研清单

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.

为每个候选名称搜索以下平台并记录URL：

SaaS / AI / 初创企业 — Crunchbase、Product Hunt，以及
```
"<name>"
```
+垂直领域的普通网页搜索。
代码命名空间 — GitHub上同名的仓库；PyPI和npm上同名的软件包。
相邻领域（最重要） —
```
"<name>"
```
+用户所属垂直领域。同一垂直领域的匹配结果会直接终止该名称的审核。
隐私/安全工具 — 若命名对象涉及数据处理则需检查。
商标及可拥有性 — 初步查询USPTO/EUIPO中相关类别下的有效商标，同时判断名称的描述性：是否足够独特可专属化，还是易被竞争对手挤占的通用复合词？
基准名称 — 若为基准命名，决定性检查是文献而非域名：该名称是否已作为公开数据集/基准存在（arXiv / ACL / Papers with Code）？引用冲突才是关键，而非域名。

输出表格：

名称	已存在的重要使用案例（URL）	是否存在相邻领域冲突？	商标/可拥有性	结论
Acme	github.com/x, acme.io（物流领域）	否	独特，无有效商标	进入候选名单

结论

选项为：进入候选名单（晋级）/ 淘汰（出局）/ 选中（最终选择）。需遵循决策规则。

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.sh
```
and trademark with a registry lookup, not with "I didn't find anything."
Rank by safety first, then ownability, then aesthetics.

相邻领域冲突→淘汰。即便所有域名都可用。同一垂直领域的竞品会彻底毁掉该名称。
描述性/通用复合词→竞争力弱。域名可能可用，但难以注册商标且SEO表现差。即便可注册，也要标注可拥有性风险。
域名免费≠安全。可用性是必要条件，但非充分条件。只有当名称同时可注册且无相邻领域及商标冲突时，才适合选用。
选中前务必验证。通过
```
check_domains.sh
```
确认域名，通过注册机构查询确认商标，而非仅凭“我没找到相关结果”。
排序优先级：安全性→可拥有性→美观度。

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.

为医疗健康/教练垂直领域的隐私-focused去标识化工具包+基准命名。候选名称：Praxio、Dyad、Sessio、ClientPII、CONFIDE。

名称	筛选测试结果	结论
Praxio	听起来不错，但Praxis EMR是医疗健康领域的电子健康记录系统——与目标垂直领域存在相邻冲突。	淘汰
Dyad	简洁且有意义，但 `dyad.sh` 是本地AI开发工具， `dyad.ai` 是医疗健康公司——在技术领域和目标垂直领域均存在冲突。	淘汰
Sessio	不错，但 `sessio.base44.app` 是面向治疗师的同领域产品。	淘汰
ClientPII	所有TLD均可用——但属于通用描述性复合词，商标注册难度大，SEO表现差。	未入选（不适合作品牌名）
CONFIDE	所有域名均已被占用（不适合作产品品牌）——但作为基准名称，引用冲突风险低。	选中（作为基准名称）

核心总结：域名免费≠安全，品牌适配≠可用。多数看似合适的名称会因域名检查无法发现的相邻领域冲突而失败。

scripts/check_domains.sh

bash

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 env

Per 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

bash

scripts/check_domains.sh praxio dyad sessio          # 默认TLD（.com .org .ai .io .app .co）
scripts/check_domains.sh praxio dyad -- com ai io     # 自定义TLD（需在--后指定）
TLDS="com org ai" scripts/check_domains.sh praxio     # 或通过环境变量指定

针对每个域名，该脚本会运行

whois

（必要时遵循IANA注册机构指引）及

dig +short NS

，生成

名称×TLD

表格，标记为

free

taken

。

表示需手动验证（WHOIS限流或

.ai

域名查询不稳定）。需确保

whois

和

dig

在PATH中（macOS默认自带；Linux需执行

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-banana
or gpt-image-2
— optional draft branding (stage 6). Draft quality by default.

firecrawl
— 冲突/文献调研（阶段3b）。禁止使用beautifulsoup。
present
— 交互式HTML选拔报告（阶段5）。需传入对比数据及单名称幻灯片内容。
nano-banana
或 gpt-image-2
— 可选草稿品牌设计（阶段6）。默认生成草稿质量内容。

Safety & limits

安全与限制

WHOIS is authoritative for registration, not trademark. A free domain can still infringe a live mark. Always do the separate trademark read.
.ai
WHOIS 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.

WHOIS仅对注册可用性权威，对商标无效。免费域名仍可能侵犯有效商标。务必单独进行商标查询。
.ai
域名的WHOIS查询不稳定。标记为
```
?
```
的结果需“通过注册商搜索确认”，而非视为“可用”。
该脚本仅证明可注册性，不代表法律许可——不涵盖商标、社交账号或应用商店冲突。若要将名称用于商业运营，需获得律师的法律许可。
品牌设计为可选功能且需用户触发——仅当用户要求时才生成logo；默认生成草稿质量内容，除非另有说明。
最终决策权在用户。该技能仅提供建议，不做最终决定。

Install

安装

Portable across Claude Code and Codex — plain-prose workflow, one bash script, no Claude-only tools.

bash

cp -R name-audition ~/.claude/skills/   # Claude Code
cp -R name-audition ~/.agents/skills/   # Codex

可在Claude Code和Codex间移植——纯文本工作流程，仅含一个bash脚本，无Claude专属工具。

bash

cp -R name-audition ~/.claude/skills/   # Claude Code
cp -R name-audition ~/.agents/skills/   # Codex