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 konglong87/superPM --skill start-super-pmgit clone --depth 1 https://github.com/konglong87/superPMWrote 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/konglong87/superpm/start-super-pm)<a href="https://agentmods.dev/skills/konglong87/superpm/start-super-pm"><img src="https://agentmods.dev/badge/skills/konglong87/superpm/start-super-pm.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00025 | $0.05546 |
| Opus 5 | $0.00013 | $0.02773 |
| Sonnet 5 | $0.00005 | $0.01109 |
| Haiku 4.5 | $0.00003 | $0.00555 |
Grade A, and why
start-super-pm 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 491 lines — stays where its author put it; the contents beside it link to each section on GitHub.
如果你认为某个产品管理 skill 有 1% 的可能性适用于当前任务，你必须调用该 skill。
如果 PM skill 适用，你没有选择，必须使用它。
这不可协商，不是可选项，你不能找借口跳过。
跨 Agent 交互规则
当流程要求与用户交互时：
- 如果当前环境支持 AskUserQuestion，使用 AskUserQuestion（最佳体验）。
- 如果当前环境不支持 AskUserQuestion，必须用普通聊天消息提出同样问题。
- 一次只问一个问题。
- 提问后必须停止当前回合，等待用户回答（STOP and WAIT）。
- 不得在用户回答前生成文档、写入 docs。
- 已有 docs 文件不能替代本轮用户回答。
常见误区 / Red Flags — STOP
出现以下情况立即停止并回溯：
| 误区 | 正确做法 |
|---|---|
| 使用"应该"、"大概"、"看起来"做结论 | 必须基于实际数据和验证 |
| 未运行检查就声称已完成 | 先验证，再陈述 |
| 因时间紧迫跳过关键步骤 | 没有例外，时间紧更要严格 |
| "这次应该没问题"的想法 | 每次都要重新验证 |
Super-PM 自动触发系统
核心规则
在任何产品管理相关的响应或行动之前，先检查并调用相关的 PM skill。
即使只有 1% 的可能性 skill 适用，也应该先调用 skill 进行检查。如果调用的 skill 不适合当前情况，不需要使用它。
如何访问 PM Skills
在 Claude Code： 使用 Skill 工具。调用 skill 时，其内容会被加载并呈现给你——直接遵循它。不要使用 Read 工具读取 skill 文件。
在其他环境： 查看你平台的文档了解如何加载 skills。
PM Skill 自动触发决策流程（详见下方各模块触发信号）
⚠️ 最高优先级路由（仅适用于自然语言请求）
当用户用自然语言提出产品管理任务（而非显式输入 /pm-xxx slash command）：
- "我想做一个XX"
- "帮我规划XX产品"
- "帮我设计一下需求"
- "从0到1做XX"
- "讨论产品方向"
默认必须进入 /pm-brainstorm。
只有用户明确说以下任一表达，才允许跳过：
- "跳过 brainstorm"
- "直接需求调研"
- "直接验证需求"
- "我已经完成头脑风暴"
agent 不得自行判断"方向明确"并跳过 /pm-brainstorm。
显式 slash command 不走此路由：当用户直接输入 /pm-demand、/pm-docs 等时，直接进入对应 skill，该 skill 自身执行前置门禁。
任务类型识别指南
🎯 需求洞察模块（自动触发 pm-demand 或相关 skill）
触发信号：
- 用户提到"需求"、"用户痛点"、"用户场景"、"用户故事"
- 用户想了解"用户想要什么"、"解决什么问题"
- 用户说"我想做一个XX"、"帮我规划XX"、"讨论产品方向"、"从零开始做XX"
- 用户提到具体产品形态但需求不明确：例如"社区"、"app"、"小程序"、"平台"、"工具"、"网站"
- 用户在收集用户反馈、用户调研
- 用户在规划用户旅程、用户画像
- 用户在持续追踪竞品动态、做竞品情报 / 竞品月报
- 用户要设计用户访谈、编写访谈提纲、做一手用户调研
自动调用的 Skills：
| 任务描述 | 自动调用 Skill | 说明 |
|---|---|---|
| "我想做一个XX"、"从零开始"、"帮我规划产品方向" | pm-brainstorm（优先） |
先发散，明确用户群和核心痛点 |
| "讨论产品方向"、"帮我想几个方案" | pm-brainstorm |
创意发散 |
| "分析一下用户痛点"、"验证这个需求" | pm-demand |
方向明确后收敛验证 |
| "看看市场情况"、"分析竞品" | pm-search --type=competitor |
竞品分析 |
| "查查行业数据"、"市场规模多大" | pm-search --type=data |
行业数据调研 |
| "这个需求优先级怎么排" | pm-priority |
优先级排序 |
| "规划 MVP"、"什么功能先做" | pm-mvp |
MVP 规划 |
| "需求池怎么管理"、"需求太多" | pm-pool |
需求池管理 |
| "用户旅程是什么"、"用户体验路径" | pm-journey |
用户旅程地图 |
| "竞品监控"、"竞品月报"、"竞品情报" | pm-competitor |
持续追踪竞品动态与异动预警 |
| "用户访谈"、"访谈提纲"、"用户调研" | pm-interview |
一手定性研究设计与执行 |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 491 lines · 25 tokens per session scan A e11350a2cf3b
start-super-pm is a skill published in the GitHub repository konglong87/superPM (62 stars, last pushed 4d ago), licensed MIT. It adds 25 tokens to every session and 5,546 once invoked, about $0.0001 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
team-tasks
Coordinate multi-agent development pipelines using shared JSON task files. Use when dispatching work across dev team agents (code-agent, test-agent, docs-agent, monitor-bot), tracking pipeline progress, or running sequential/parallel workflows. Covers project init, task assignment, status tracking, agent dispatch via…
multi-search
A web-search helper that chooses among DuckDuckGo, Tavily, Bing API, and Bing scraping based on the available network.
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
slack-construct-agents
Standing context for Slack sibling agents — one room per team, creator-posted introductions, bot-to-bot hop discipline. Ships as instructions.md composed into the group's CLAUDE.md at spawn; there is no workflow to invoke.
clawteam
Multi-agent swarm coordination via the ClawTeam CLI. Use when the user wants to create agent teams, spawn multiple agents to work in parallel, coordinate tasks with dependencies, broadcast messages between agents, monitor progress via kanban board, or launch pre-built team templates (hedge-fund, code-review…