Token导航 LogoToken导航

Agent Skill · 研究检索

business-naming(企业命名)

business-naming 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

business-naming 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 55,679。

总安装 470周安装 19GitHub Stars 1下载 147核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:business-naming(企业命名)
来源仓库:https://github.com/theepan/ai-agent-skills
仓库路径:skills/business-naming
安装命令:
npx skills add https://github.com/theepan/ai-agent-skills --skill business-naming
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/theepan/ai-agent-skills --skill business-naming

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

采用 Identify-Invent-Implement 三阶段流程生成品牌名称。注重名称的故事性与行为经验 grounding 的差异化特征。支持候选名称的快速筛选与框架适配度评估功能。business-naming 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

需明确业务本质与目标用户以建立正确的命名方向。输出包含语音测试与法律风险的完整命名决策支持报告。

来源仓库内路径:skills/business-naming

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/theepan/ai-agent-skills --skill business-namin…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

business-naming 怎么安装?

在终端执行 npx skills add https://github.com/theepan/ai-agent-skills --skill business-naming。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

business-naming 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

business-naming 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

business-naming 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

business-naming 用的人多吗?

公开数据是累计安装 470 次,近一周安装 19 次,下载 147 次,GitHub 1 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

business-naming 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
business-naming

企业命名 · 本页

4701只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Business Naming

Generate and evaluate names using a structured three-phase process: Identify (set the framework), Invent (generate and filter), Implement (test and select). Aim for names that are distinctive, grounded in behavior and experience, and that start a story.

Input Handling

Determine what the user needs and gather context accordingly:

  1. New name -- User describes a business, product, or brand that needs a name. Run all three phases.
  2. Shortlist evaluation -- User provides candidate names to evaluate. Skip to Phase 3 (Implement), but run a quick Phase 1 (Identify) to establish the framework for evaluation.
  3. Brief creation -- User wants a creative brief for naming. Run Phase 1 (Identify) and deliver the brief as the output.
  4. Rename -- Existing name needs replacing. Run all three phases, adding the current name and its problems to the landscape analysis.

If the user provides minimal context, ask targeted questions to fill gaps. At minimum you need: what is being named, who it serves, and what makes it different.

Naming Process

Execute these phases in order.

Phase 1: Identify -- Set the Framework

Focus on behavior and experience, not mission statements.

Read references/diamond-exercise.md before this phase.

1a. Analyze Behavior

Establish three perspectives:

  • Current behavior -- How does the company/product behave today? How do users interact with it? What is the experience?
  • Desired behavior -- How should it behave? What experience should users have?
  • Market response -- How does the market currently perceive the category? What language and expectations exist?
1b. Map the Landscape

Study the competitive naming landscape:

  • List competitor names and the language patterns they use (e.g., real estate: Home, Find, Key, Nest, Roof, Door).
  • Identify the cliches and overused words in the category.
  • Define what the name must not sound like. A name that blends in with competitors is "a form of suicide."
1c. Creative Framework

Create a "metaphorical window" -- a short phrase that opens creative possibilities without locking in narrow objectives.

Format: [Core feeling] + [Action/arrival] + [Defining moment]

Example: "Clarity + arrival + the moment you know" (for a real estate site).

1d. Diamond Exercise

For startups or when context is limited, define what the name must achieve using the Diamond:

CornerQuestion
WinWhat does winning look like for the company?
What you have to winCurrent assets and strengths
What you need to winGaps and resources needed
What you have to sayThe one thing the market must hear

Use the Diamond as the naming brief, not a generic mission statement.

Phase 2: Invent -- Generate and Filter

Volume first, then filter ruthlessly.

Read references/sound-symbolism.md and references/forced-synchronicity.md before this phase.

2a. Sound Symbolism

Select target letter/sound associations that match the desired behavior:

Letter/SoundAssociationUse when you want...
VAlive, vibrantEnergy, movement, life
BReliable, solidTrust, dependability
Z, SSignal, sharpClarity, precision, cutting through noise
K, hard CCrisp, strongAuthority, impact
LSmooth, lightElegance, ease
RAction, forcePower, motion
M, NWarm, groundedComfort, familiarity
TPrecise, tightEfficiency, sharpness
PPunchy, readyEnergy, pop

Use as a lens for filtering, not a rigid rule.

2b. Three-Brief Strategy

Generate names from three different angles to escape category thinking:

  • Brief A (Real) -- The actual brief from Phase 1. Generate names that directly address the behavior, framework, and Diamond.
  • Brief B (Competitor) -- Imagine you are naming for a major competitor. What names would you generate for them? This produces names the category expects but may surface strong options.
  • Brief C (Unrelated) -- Imagine you are naming something completely unrelated (a bicycle, a restaurant, a sailing company). This breaks category cliches and produces the freshest candidates.
2c. Forced Synchronicity

Mine 2-3 domains unrelated to the category for unexpected metaphors:

  • Browse their language, visuals, and naming patterns.
  • Note words, phrases, or metaphors that map onto the brand's behavior.
  • Use these as seeds so names don't sound like the category.

Example: For a trades automation tool, borrow from music (cadence, tempo), sailing (bearing, trim), and sports (relay, baton).

2d. Generate at Volume

Produce a large number of candidates (aim for breadth, not perfection):

  • Mix real words, metaphors, compounds, coined words, and borrowed terms.
  • Vary length (1-3 syllables preferred for recall).
  • Include unexpected directions from Brief C and forced synchronicity.
2e. Filter

Apply these filters in order:

  1. Distinctiveness -- Does it stand apart from the competitive landscape? Remove anything that sounds like the category.
  2. Story potential -- Does it invite a line of explanation? "We're called X because..." should feel natural and interesting.
  3. Sound check -- Does the sound match the desired behavior? (Use the sound symbolism lens.)
  4. Practical screens -- Is it pronounceable? Spellable? Free of negative associations in key markets? Short enough?

Note: Legal and trademark screening is for the user to do later. Flag obvious conflicts but do not eliminate names solely on trademark speculation.

Phase 3: Implement -- Test and Select

Get the name into context; test what it makes people imagine.

3a. Present with Context

For each recommended name, provide:

  • The name
  • Why it works -- How it connects to the behavior and framework from Phase 1
  • Sound/metaphor -- What sonic and metaphorical qualities it carries
  • In context -- A sample tagline, headline, or usage ("Welcome to X", "Built on X", "X: [tagline]") so the user can feel the "lift"
3b. Structure the Shortlist

Organize names into tiers:

  • Top recommendations (5-10) -- Strongest candidates with full rationale
  • Strong alternatives (5-10) -- Good options worth considering
  • Honorable mentions -- Names with potential that didn't make the cut, with brief notes on why
3c. Evaluation Guidance

If the user is testing names with others, advise:

  • Ask: "What does this name make you imagine about the product?" This tests predisposition to consider, not subjective preference.
  • Do not ask "Do you like it?" -- this produces unreliable data.
  • Embrace polarization -- Mixed love/hate reactions are a strength. "No power in comfort." A name that everyone "kind of likes" is probably weak. A name that some love and some question has signal.

Output Format

Structure the naming deliverable as follows:

Brief

Summarize the framework from Phase 1: behavior (current, desired, market), landscape to avoid, creative framework, and Diamond (if applicable). This grounds the name recommendations.

Sound Direction

State the target sound associations and forced synchronicity sources used.

Shortlist

Present names in a table:

NameWhy it worksSound / metaphor
NameConnection to behavior and frameworkSound associations and source metaphor

Organize into Top recommendations and Strong alternatives.

For each top recommendation, include a sample usage line showing the name in context (tagline, headline, or sentence).

Principles Applied

Briefly confirm which naming principles drove the selections:

  • Distinctive > comfortable
  • Behavior and experience over abstract values
  • Name starts the story
  • Sound symbolism alignment

Next Steps

Recommend concrete next steps:

  1. Prototype -- Where to show the name (mock ad, app icon, business card, etc.)
  2. Research -- The right question to ask ("What does this name make you imagine about the product?")
  3. Legal/trademark -- Screen the shortlist
  4. Polarization -- How to interpret mixed reactions

Guidelines

  • Ground every name in the behavior and experience established in Phase 1. Names should connect to how people act and feel, not abstract corporate values.
  • Prioritize distinctiveness. If a name could belong to any competitor in the category, it is too generic. Challenge yourself to escape category language.
  • Show your work. Walk the user through the framework, landscape, and creative decisions so they understand why each name was recommended.
  • Generate with volume. Do not stop at 5 obvious names. Explore unexpected directions through forced synchronicity and the three-brief strategy.
  • Present names in context. A name on its own is abstract; a name in a tagline, headline, or mock usage comes alive.
  • When evaluating existing names, apply the same framework: Does it connect to behavior? Is it distinctive? Does it start a story?
  • Treat polarization as signal, not noise. If the user reports mixed reactions, reframe that as a positive indicator of memorability and story potential.
  • Flag obvious trademark conflicts but do not speculatively eliminate names. Legal screening is the user's responsibility.
  • When uncertain about the business, market, or user intent, ask rather than assume. A good brief produces better names than a guessed brief.

平台分布

Codex

37.36%
按下载量换算55

Claude

31.14%
按下载量换算46

Cursor

19.06%
按下载量换算28

Gemini CLI

8.95%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills