User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
产品命名协作流程。当用户想给产品/项目/模块起名字时使用。通过"灵魂挖掘 → 约束提取 → 路线发散 → 方向选择 → 竞品验证 → 最终确认"的结构化流程，从模糊想法产出有品牌生命力的名字，避免拍脑袋起名。
Install Product Naming
$ npx skills add yunshu0909/yunshu_skillshub --skill product-naming -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yunshu0909/yunshu_skillshub product-naming --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/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/brand/product-naming .claude/skills/product-naming && 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 "product-naming" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/brand/product-naming into .claude/skills/product-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-naming", 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/yunshu0909/yunshu_skillshub/tree/master/brand/product-namingType 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 yunshu0909/yunshu_skillshub --skill product-naming -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yunshu0909/yunshu_skillshub product-naming --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/brand/product-naming .agents/skills/product-naming && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "product-naming" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/brand/product-naming into .agents/skills/product-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-naming", 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 yunshu0909/yunshu_skillshub --skill product-naming -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yunshu0909/yunshu_skillshub product-naming --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/brand/product-naming .cursor/skills/product-naming && 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 "product-naming" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/brand/product-naming into .cursor/skills/product-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-naming", 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/yunshu0909/yunshu_skillshub.git --path brand/product-naming--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 yunshu0909/yunshu_skillshub --skill product-naming -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yunshu0909/yunshu_skillshub product-naming --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/brand/product-naming .gemini/skills/product-naming && 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 "product-naming" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/brand/product-naming into .gemini/skills/product-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-naming", 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 yunshu0909/yunshu_skillshub product-namingInstalls 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 yunshu0909/yunshu_skillshub --skill product-naming -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .github/skills && cp -r skills-src/brand/product-naming .github/skills/product-naming && 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 "product-naming" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/brand/product-naming into .github/skills/product-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-naming", 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 yunshu0909/yunshu_skillshub --skill product-naming -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yunshu0909/yunshu_skillshub product-naming --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yunshu0909/yunshu_skillshub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/brand/product-naming .opencode/skills/product-naming && 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 "product-naming" agent skill from https://github.com/yunshu0909/yunshu_skillshub/tree/master/brand/product-naming into .opencode/skills/product-naming/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-naming", 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
product-naming- GitHub stars
- 768
- Used in
- 1 other repo
- Token cost
- ~724 tokens
- SKILL.md length
- 164 words
- Files
- 1
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- MIT
At a glance
产品命名协作流程。当用户想给产品/项目/模块起名字时使用。通过"灵魂挖掘 → 约束提取 → 路线发散 → 方向选择 → 竞品验证 → 最终确认"的结构化流程，从模糊想法产出有品牌生命力的名字，避免拍脑袋起名。
- Works in 5 steps: 用户是谁？ — 什么人在用？什么场景下用？使用频率？ → 产品本质 — 用一句话介绍这个产品是什么？（不是功能列表，是角色/定位/比喻） → 产品边界 — 做什么、不做什么、未来往哪个方向长？ → …
- Product & Project Management work in your project
- SKILL.md covers 核心原则, 工作流程 and 沟通规范
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Product Naming is an agent skill from yunshu0909/yunshu_skillshub. 产品命名协作流程。当用户想给产品/项目/模块起名字时使用。通过"灵魂挖掘 → 约束提取 → 路线发散 → 方向选择 → 竞品验证 → 最终确认"的结构化流程，从模糊想法产出有品牌生命力的名字，避免拍脑袋起名。
Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management. The repository describes itself as: 云舒精选的 Claude Code Skills 集合，提升开发和产品管理效率. The licence is MIT.
When your agent uses it
- Product & Project Management work in your project
Example prompts
- “灵魂挖掘 → 约束提取 → 路线发散 → 方向选择 → 竞品验证 → 最终确认”
- “/product-naming”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- 用户是谁？ — 什么人在用？什么场景下用？使用频率？
- 产品本质 — 用一句话介绍这个产品是什么？（不是功能列表，是角色/定位/比喻）
- 产品边界 — 做什么、不做什么、未来往哪个方向长？
- 品牌气质 — 用户看到这个名字时，应该有什么第一反应？（专业/亲切/极客/轻松/...）
- 硬性约束 — 语言偏好？长度限制？需要避开的词？
What it can do on your machine
Read from SKILL.md and the folder at commit da0d31f. 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
No scripts in the folder and no shell commands in SKILL.md.
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
Product Naming loads about 724 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 164 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from yunshu0909/yunshu_skillshub at commit da0d31f, republished under its MIT licence (© yunshu0909). 164 words, ~724 tokens.
Download SKILL.mdSave it as
.claude/skills/product-naming/SKILL.md (or your agent's skills folder).- name
- product-naming
- description
- 产品命名协作流程。当用户想给产品/项目/模块起名字时使用。通过"灵魂挖掘 → 约束提取 → 路线发散 → 方向选择 → 竞品验证 → 最终确认"的结构化流程，从模糊想法产出有品牌生命力的名字，避免拍脑袋起名。
- metadata.status
- active
- metadata.status_updated_at
- 2026-10-06
用户想给产品、项目或模块起一个名字，但还没想好叫什么。通过结构化的协作流程，从产品本质出发推导名字，而不是直接列一堆候选词让用户挑。
核心原则
- 先想清楚再起名 — 没有理解产品灵魂之前，绝不列候选名字
- 名字是推导出来的，不是拼凑出来的 — 从产品定位、用户画像、品牌气质中自然推导
- 给路线，不给列表 — 先让用户选命名方向，再在方向内发散具体名字
- 用数据验证直觉 — 调研同赛道产品的命名规律，避免闭门造车
- 不催不赶 — 名字是品牌的根基，值得花时间想清楚
工作流程
第 1 步：产品灵魂挖掘（不碰名字）
这一步的目标是理解产品的本质，而不是收集功能列表。
主动了解项目背景（读代码、读文档），然后向用户追问以下问题：
- 用户是谁？ — 什么人在用？什么场景下用？使用频率？
- 产品本质 — 用一句话介绍这个产品是什么？（不是功能列表，是角色/定位/比喻）
- 产品边界 — 做什么、不做什么、未来往哪个方向长？
- 品牌气质 — 用户看到这个名字时，应该有什么第一反应？（专业/亲切/极客/轻松/...）
- 硬性约束 — 语言偏好？长度限制？需要避开的词？
关键：如果用户给出一个比喻（比如"像 Jarvis"），一定要深挖这个比喻背后的含义——它揭示的是用户对产品角色的想象。
禁止：
- 读完项目文档就开始列名字
- 问一个问题就觉得够了，必须把以上问题都覆盖到
- 把这些问题当表单一次性丢给用户，应该是自然对话
第 2 步：命名约束提取
从第 1 步的回答中提取：
- 关键词 — 从用户的描述中提炼核心语素（如：编程、助手、伙伴、工具、管理）
- 识别张力 — 用户的多个诉求之间是否存在矛盾？（如"要像人名一样有温度" vs "一眼看出跟编程有关"）
- 明确优先级 — 如果有张力，哪个诉求优先？
向用户展示你的分析，确认理解无误。
示例：
你的核心诉求：
- ✅ 让人知道跟团队协作有关
- ✅ 轻松不严肃，不像企业软件
- ⚡ 这两个有张力：协作类名字容易显得"企业味重"，轻松的名字又容易看不出用途
我的判断是"轻松感"优先，因为你要跟 Slack/钉钉竞争的是体验而非功能。对吗？禁止：跳过分析直接出名字。这一步是从"感觉"到"逻辑"的关键桥梁。
第 3 步：路线发散
基于约束分析，推导出 2-4 条命名路线，每条路线代表一种不同的命名策略。
每条路线包含：
- 路线名称 — 一句话概括这条路的思路
- 2-3 个示意名字 — 让用户感受这个方向的味道
- 优缺点 — 诚实说明每条路的利弊
示例：
路线 A：拟声/动作词
示意：Ping、Holler、Nudge
✅ 轻快、有画面感
❌ 不直接关联"站会"场景
路线 B：时间/节奏隐喻
示意：DayBeat、MorningSync、Cadence
✅ 暗示每日节奏，贴合站会频率
❌ 偏长，组合感强
路线 C：缩写/造词
示意：Stanly（standup + daily）、Asynco（async + co）
✅ 独特好注册
❌ 需要解释含义禁止：
- 只给一条路线
- 路线之间差异太小
- 不说缺点，只说好话
- 在这一步列超过 5 个具体名字/路线（让用户选方向，不是选名字）
第 4 步：用户选择方向
用户可以：
- 直接选一条路线
- 组合多条路线的元素（"C 的直接 + A 的温度"）
- 全部否掉，补充新方向 → 回到第 3 步
选定方向后，在该方向内深挖 3-5 个具体候选名字，每个附带一句话解释。
禁止：用户选了方向之后还在其他方向上发散。聚焦。
第 5 步：竞品验证 + 命名策略
用户倾向某个名字后，做两件事：
5a. 竞品命名调研
搜索同赛道产品的命名规律：
- 纯英文 / 中英文双品牌 / 纯中文，哪种多？
- 名字长度？音节数？
- 有没有撞名风险？
5b. 命名策略确认
基于调研结果，向用户建议：
- 需要几个名字？（英文名 + 中文名？还是只要一个？）
- 要不要 slogan？
- 理由是什么？
示例：
调研发现同赛道的 Geekbot、Range、Standuply 都只用一个英文名。
建议：只用 Ping，不另起中文名。
理由：用户是开发团队，日常沟通已经用英文工具；一个音节最好记。
如果需要中文场景，加 slogan："Ping — 轻拍一下，站会搞定"禁止：不做调研就建议命名策略，所有建议必须有数据支撑。
第 6 步：最终确认
汇总整个过程的决策链路，输出最终结论：
📌 产品名称：Ping
📌 Slogan：轻拍一下，站会搞定
📌 命名策略：纯英文单品牌
📌 决策依据：
- 用户画像：远程开发团队
- 产品定位：替代每日站会的异步同步工具
- 核心约束：轻松不严肃，一看就想用
- 竞品惯例：同赛道主流为纯英文短名称沟通规范
必须问用户的
| 时机 | 问什么 |
|---|---|
| 第 1 步 | 用户画像、产品本质、产品边界、品牌气质、硬性约束 |
| 第 3 步 | 选哪条路线 |
| 第 4 步 | 倾向哪个具体名字 |
| 第 5 步 | 命名策略是否认同（几个名字、要不要 slogan） |
| 第 6 步 | 最终确认 |
不需要问用户的
| 事项 | 直接做 |
|---|---|
| 读项目文档了解背景 | 直接读，带着理解去问用户 |
| 竞品调研 | 直接搜索，带着数据给建议 |
| 分析诉求之间的张力 | 直接分析，向用户确认判断 |
AI 绝不应该做的
- 读完项目文档就甩一个名字列表
- 没有理解产品本质就开始起名
- 只从"好不好听"角度评价名字，不从品牌策略角度分析
- 用户说"不好"的时候换一批名字再来，而不是反思流程哪里出了问题
- 为了显得专业而列过多选项，造成选择瘫痪
- 催用户赶快做决定
© yunshu0909, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in brand/product-naming of yunshu0909/yunshu_skillshub.
Open the folder on GitHubat commit da0d31f
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in yunshu0909/yunshu_skillshub, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Product Naming 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 |
|---|---|---|---|---|---|---|
| Product Naming this skillyunshu0909/yunshu_skillshub | 768 | 1 repos | ~724 | Automated safety check: Pass | MIT | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Game Changing FeaturesopenstatusHQ/data-table-filters | 2.3k | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Convex Create Componentspokvulcan/poker-planning | 115 | 8 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Self Improving Agentfarm-fe/farm | 5.6k | 2 repos | ~3.3k | Automated safety check: Notes | MIT |
Similar skills
Game Changing Features
openstatusHQ/data-table-filters
Find 10x product opportunities and high-leverage improvements.
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Convex Create Component
spokvulcan/poker-planning
Builds reusable Convex components with isolated tables and app-facing APIs.
Self Improving Agent
farm-fe/farm
A universal self-improving agent that learns from ALL skill experiences.
Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
More from yunshu0909/yunshu_skillshub
All 25 skills in this repoDual Agent Collaboration
yunshu0909/yunshu_skillshub
让 Codex 与 Claude Code 通过本机 CLI 组成“主执行者 + 独立审查者”的对称协作闭环。用于用户要求两个模型一起完成、交叉校核、独立审查、修到 ACK，或任务涉及产品需求收敛、复杂方案、跨模块开发、迁移、安全、重要重构和高质量交付时；无论从 Codex 还是 Claude Code 启动，都由当前模型主持，并完整调用另一方完成需求挑战、方案门禁、实现冷审和最终验收。
Image Assistant
yunshu0909/yunshu_skillshub
配图助手 - 把文章/模块内容转成统一风格、少字高可读的 16:9 信息图提示词；先定“需要几张图+每张讲什么”，再压缩文案与隐喻，最后输出可直接复制的生图提示词并迭代。
Page Solution Design
yunshu0909/yunshu_skillshub
和用户一起敲定一个前端页面的整页方案（三层法：先定这页给用户什么，再定含哪几样怎么排，最后才是长什么样），最后打成一个定稿包（含高保真全状态与交互流程图）交给开发。触发：用户对一个页面说「想重做 / 重新设计 / 整页不对 / 太满 / 说不清具体改哪」，或「我们讨论一下这页怎么设计」。覆盖三种情形：① 已有页面整页重做；②「替换」——新方案占用同一个入口（同一路由 /…
Backend Logic Design
yunshu0909/yunshu_skillshub
和用户一起把一个功能「看不见的部分」敲定：数据存哪、谁写谁读、怎么加载、怎么保存、默认值和升级、核心执行规则、出问题时怎么办、旧东西怎么迁。每条规则带编号、案例和状态（已定 / 方案里有但你没拍板 / 待你定 / AI 定），用户只回答带案例的新选择题、过目没拍过板的规则；给用户看的是按「你会问的问题」分组的问答卡片（最绕的逻辑配可点的模拟器）；最后请另一家模型只读查边界，问题闭环后封成后端逻辑…
Article Study
yunshu0909/yunshu_skillshub
带用户精读一篇文章/文档并真正学透（不是出摘要）。五步：抽干货 → 切讲次 → 每讲跑「学-考-讲」循环 → 对号入座 → 实操+测验+讲错题+蒸馏。每讲产出 HTML 课件 + 笔记落盘；讲完必考一次，用户复述后必须挑不精确处拧紧；抽象概念上可交互演示（能点能跑）；全程用用户自己的业务场景当案例；学完出多题型自动判分测验卷，最后把收获蒸馏回用户的工具。核心触发条件是用户要的是"学会"而不是"要…
Issue Pool
yunshu0909/yunshu_skillshub
Issue 池全生命周期管理（开发范式 v1 规划段）。核心是一条 issue 驱动的流程：用户随手丢想法，你把糊的 issue 变成能开工的 task——产出的是“问题定义”，不是“解决方案实现”；载体就是仓库根的 ISSUES.md。五个动作：记、并、拆、转、pending。规划规模只区分 single-task（一个版本能交付）与 roadmap（需要多批滚动），不得使用…
Related
Categories
Questions about Product Naming
What does Product Naming do?
产品命名协作流程。当用户想给产品/项目/模块起名字时使用。通过"灵魂挖掘 → 约束提取 → 路线发散 → 方向选择 → 竞品验证 → 最终确认"的结构化流程，从模糊想法产出有品牌生命力的名字，避免拍脑袋起名。. Product Naming is an agent skill from yunshu0909/yunshu_skillshub.
When should I use Product Naming?
Product Naming fits situations like: product & Project Management work in your project.
How do I install Product Naming in Claude Code?
Run `npx skills add yunshu0909/yunshu_skillshub --skill product-naming -a claude-code`. Or copy the skill folder (brand/product-naming in yunshu0909/yunshu_skillshub) into .claude/skills/product-naming in your project. Claude Code loads it when a task matches its description.
How do I install Product Naming in Codex?
Run `npx skills add yunshu0909/yunshu_skillshub --skill product-naming -a codex`. Or copy the skill folder (brand/product-naming in yunshu0909/yunshu_skillshub) into .agents/skills/product-naming in your project. Codex loads it when a task matches its description.
Can I use Product Naming 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 yunshu0909/yunshu_skillshub --skill product-naming -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-naming, .gemini/skills/product-naming, .github/skills/product-naming and .opencode/skills/product-naming in your project.
What does Product Naming need to run?
SKILL.md names no scripts, command-line tools or credentials: Product Naming is instructions for the agent only.
Does Product Naming 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 Product Naming 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. Review the folder before installing.
What licence does Product Naming use?
Product Naming 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 Product Naming use?
About 724 tokens (SKILL.md is roughly 2.9k 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 Product Naming?
Skills that share tags, products or a category with Product Naming: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Product Naming?
yunshu0909 (a GitHub user) maintains it in yunshu0909/yunshu_skillshub, which has 768 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 6, 2026.
Source: yunshu0909/yunshu_skillshub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.