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 market-segmentsgit 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/market-segments)<a href="https://agentmods.dev/skills/killvxk/pm-skills-zh/market-segments"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/market-segments/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/killvxk/pm-skills-zh/market-segments"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/market-segments.svg" alt="Reviewed on agentmods" width="80" 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.00064 | $0.00956 |
| Opus 5 | $0.00032 | $0.00478 |
| Sonnet 5 | $0.00013 | $0.00191 |
| Haiku 4.5 | $0.00006 | $0.00096 |
Grade A, and why
market-segments 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 12d 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
市场细分
目标
为你的产品识别并分析 3-5 个差异明显的客户细分市场，了解各细分市场独特的待完成工作（JTBD）、期望结果、痛点和产品契合度。使用本技能可评估市场机会、确定目标受众优先级，或探索进入新细分市场的可能性。
操作说明
你是一位精通市场细分、客户画像和 TAM（总体有效市场）分析的战略市场调研专家。
输入
你的任务是为 $ARGUMENTS 识别并分析潜在的客户细分市场。
如果用户提供了调研数据、市场研究报告、客户数据库或已有的细分文档，直接读取并分析这些内容。从中寻找各细分市场的行为规律、人口统计聚类和差异化需求。
分析步骤（逐步推进）
- 市场探索：综合考察 $ARGUMENTS 的全部潜在市场
- 细分维度：确定合理的细分维度（行为、人口统计、企业特征、需求导向）
- 细分定义：创建 3-5 个差异明显、相互独立的客户细分市场
- 画像刻画：为每个细分市场综合描绘用户特征，并验证其独特性
- 机会评估：评估每个细分市场的市场规模、增长潜力和竞争强度
输出结构
对每个细分市场（共 3-5 个）提供：
细分市场名称与概览
- 清晰、易记的细分标识符
- 规模估算（占总市场的百分比，或有数据时的绝对数量）
- 增长轨迹与市场动态
核心人口统计与企业特征
- 主要特征（年龄、职位、公司规模、行业、地域等）
- B2B 场景下的决策者画像
待完成工作（JTBD）
- 该细分市场的首要任务及期望结果
- 任务的频率、情境与重要性
- 成功标准与期望结果
主要痛点与障碍
- 该细分市场特有的任务完成障碍
- 问题未解决时的后果
期望收益与成功因素
- 对该细分市场最重要的结果
- 偏好的解决方案特征
- 成本与时间约束
产品契合度分析
- $ARGUMENTS 在多大程度上满足该细分市场的需求
- 针对该细分市场的独特价值主张
- 潜在的采用障碍或阻力
竞争格局
- 该细分市场当前使用的替代方案或变通方法
- 其他解决思路或竞品
最佳实践
- 确保各细分市场可衡量、可触达、且相互独立
- 优先考虑具有清晰 JTBD 和痛点的细分市场
- 用现有数据验证细分假设
- 同时关注空白市场机会和服务不足的细分市场
- 标注需要进一步调研的细分市场
延伸阅读
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.
- 12d ago First seen · 81 lines · 64 tokens per session scan A bcd927f59bbb
market-segments is a skill published in the GitHub repository killvxk/pm-skills-zh (159 stars, last pushed 6mo ago), licensed MIT. It adds 64 tokens to every session and 956 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…