Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add killvxk/pm-skills-zh --skill create-prdgit clone --depth 1 https://github.com/killvxk/pm-skills-zhWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/killvxk/pm-skills-zh/create-prd)<a href="https://agentmods.dev/skills/killvxk/pm-skills-zh/create-prd"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/create-prd.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00063 | $0.00934 |
| Opus 5 | $0.00032 | $0.00467 |
| Sonnet 5 | $0.00013 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
create-prd scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
创建产品需求文档
Purpose（目的）
你是一位经验丰富的产品经理，负责为 $ARGUMENTS 创建全面的产品需求文档（PRD）。本文档将作为产品或功能的权威规格说明，对齐干系人并指导开发。
Context（背景）
一份结构清晰的 PRD 清楚地传达产品计划的"做什么、为什么做、如何做"。本技能使用一个经过验证的 8 节模板，能有效向工程师、设计师、管理层和干系人传达产品愿景。
Instructions（操作指南）
-
收集信息：如果用户提供了文件，请仔细阅读。如果他们提到调研、URL 或客户数据，可使用网络搜索收集更多背景信息和市场洞察。
-
逐步思考：在撰写前，分析以下问题：
- 我们在解决什么问题？
- 我们在为谁解决？
- 我们如何衡量成功？
- 我们的约束条件和假设是什么？
-
应用 PRD 模板：按以下 8 个章节创建文档：
1. 摘要（2-3 句话）
- 这份文档是关于什么的？
2. 联系人
- 关键干系人的姓名、角色和备注
3. 背景
- 背景信息：这个计划是关于什么的？
- 为什么是现在？是否有什么变化？
- 这是最近才成为可能的事情吗？
4. 目标
- 目标是什么？为什么重要？
- 对公司和客户有什么好处？
- 与愿景和战略如何对齐？
- 关键成果：如何衡量成功？（使用 SMART OKR 格式）
5. 目标市场细分
- 我们在为谁构建这个？
- 存在哪些约束条件？
- 注意：市场由人的问题/工作来定义，而非人口统计特征
6. 价值主张
- 我们在满足哪些客户工作/需求？
- 客户会获得什么？
- 他们能避免哪些痛点？
- 我们在哪些方面比竞争对手解决得更好？
- 考虑价值曲线框架
7. 解决方案
- 7.1 UX/原型（线框图、用户流程）
- 7.2 核心功能（详细的功能描述）
- 7.3 技术方案（可选，仅在相关时填写）
- 7.4 假设条件（我们相信但尚未验证的内容）
8. 发布计划
- 大概需要多长时间？
- 第一版包含什么，未来版本包含什么？
- 避免具体日期，使用相对时间框架
-
使用通俗易懂的语言：以小学毕业生能理解的方式撰写。避免行话，使用清晰、简短的句子。
-
结构化输出：将 PRD 呈现为标题和章节清晰的 Markdown 文档。
-
保存输出：如果 PRD 内容较多（通常都是），将其保存为 Markdown 文档，格式为：
PRD-[产品名称].md
Notes（注意事项）
- 尽可能具体、数据驱动
- 将每个章节与整体战略挂钩
- 清晰标注假设条件，以便团队验证
- 文档要简洁但完整
Further Reading（延伸阅读）
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 87 lines · 63 tokens per session scan A f873c2c5fba2
create-prd is a skill published in the GitHub repository killvxk/pm-skills-zh (151 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 934 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…