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 agentmods add skills/echovic/boss-skill/competitive-analysisnpx skills add echoVic/boss-skill --skill competitive-analysisgit clone --depth 1 https://github.com/echoVic/boss-skillWhat 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 | $0.00030 | $0.01819 |
| Opus 5 | $0.00015 | $0.00910 |
| Sonnet 5 | $0.00006 | $0.00364 |
| Haiku 4.5 | $0.00003 | $0.00182 |
Grade A, and why
pm/competitive-analysis 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 3d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
竞品调研与分析方法论
适用场景
在产品设计前或迭代时，需要了解市场上已有的解决方案，学习竞品的优点，发现竞品的不足，找到差异化机会。
核心方法
1. 竞品识别
直接竞品：解决相同问题、服务相同用户的产品 间接竞品：解决相似问题或服务相似用户的产品 潜在竞品：未来可能进入该领域的产品
识别方法：
- 使用
WebSearch搜索关键词："{功能} + 工具/软件/平台" - 搜索 "best {功能} tools 2026"
- 搜索 "{功能} alternatives"
- 查看行业报告和评测文章
2. 竞品分析框架
对每个竞品，从以下5个维度进行分析：
2.1 功能维度
| 分析点 | 问题 |
|---|---|
| 核心功能 | 主要解决什么问题？ |
| 功能广度 | 覆盖了哪些场景？ |
| 功能深度 | 每个功能做到什么程度？ |
| 功能缺失 | 用户期望但没有的功能？ |
2.2 体验维度
| 分析点 | 问题 |
|---|---|
| 易用性 | 新用户能快速上手吗？ |
| 流畅度 | 完成任务的步骤多吗？ |
| 视觉设计 | 界面美观吗？符合用户审美吗？ |
| 交互设计 | 交互符合直觉吗？有惊喜吗？ |
| 性能表现 | 加载快吗？响应及时吗？ |
2.3 用户维度
| 分析点 | 问题 |
|---|---|
| 目标用户 | 主要服务哪类用户？ |
| 用户评价 | 用户喜欢什么？抱怨什么？ |
| 用户规模 | 有多少用户？增长如何？ |
| 用户粘性 | 用户活跃度如何？留存如何？ |
2.4 商业维度
| 分析点 | 问题 |
|---|---|
| 商业模式 | 如何赚钱？ |
| 定价策略 | 价格如何？用户接受度如何？ |
| 市场定位 | 高端还是大众？ |
| 竞争优势 | 核心壁垒是什么？ |
2.5 技术维度
| 分析点 | 问题 |
|---|---|
| 技术架构 | 使用什么技术栈？ |
| 技术创新 | 有技术上的创新吗？ |
| 技术限制 | 技术上有什么局限？ |
3. 竞品对比分析
使用 WebFetch 深入分析竞品后，整理为对比表格：
| 竞品 | 核心功能 | 用户体验亮点 | 用户痛点 | 我们的机会 |
|---|---|---|---|---|
| [竞品 1] | [功能] | [亮点] | [痛点] | [机会] |
| [竞品 2] | [功能] | [亮点] | [痛点] | [机会] |
| [竞品 3] | [功能] | [亮点] | [痛点] | [机会] |
关键要点：
- 核心功能：简洁描述，不超过3个
- 用户体验亮点：值得学习的地方
- 用户痛点：从用户评价中提取真实痛点
- 我们的机会：基于痛点，我们可以如何做得更好
4. 差异化策略
基于竞品分析，制定差异化策略：
| 维度 | 竞品做法 | 我们的做法 | 差异化价值 |
|---|---|---|---|
| [维度 1] | [做法] | [做法] | [价值] |
| [维度 2] | [做法] | [做法] | [价值] |
差异化维度示例：
- 功能差异：提供竞品没有的功能
- 体验差异：同样的功能，更好的体验
- 定位差异：服务不同的用户群体
- 价格差异：不同的定价策略
- 技术差异：使用更先进的技术
调研工具使用
WebSearch 使用技巧
搜索竞品：
"{功能} tools"
"best {功能} software 2026"
"{竞品名} alternatives"
"{竞品名} vs {竞品名}"
搜索用户评价：
"{竞品名} review"
"{竞品名} pros and cons"
"{竞品名} reddit" (Reddit上的真实讨论)
搜索行业趋势：
"{行业} trends 2026"
"{行业} market report"
WebFetch 使用技巧
深度分析竞品：
- 访问竞品官网，了解产品定位和核心功能
- 访问竞品定价页面，了解商业模式
- 访问用户评价网站（如 G2, Capterra），了解用户反馈
- 访问竞品博客，了解产品演进方向
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.
- 3d ago First seen · 197 lines · 30 tokens per session scan A 0cfd08df5944
pm/competitive-analysis is a skill published in the GitHub repository echoVic/boss-skill (553 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 1,819 once invoked, about $0.0002 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
large-workspace-handling
To partition large workspaces (100+ files) into scoped subagent tasks when context is insufficient.
example-skill
Example skill template used for the CreateHub template. You should never use this skill directly as it is just a template made to be updated.
bmad-github-story-dev
Set up a git worktree/branch (or reuse the current one) and run BMAD dev-story end-to-end: auto-commits per task, PR creation, label updates. Use when the user invokes the SD menu code in bmad help, or asks to start implementing the next ready story, or asks to begin dev on a story.
bmad-github-story-sync
Reconcile GitHub state with BMAD files — detect merged PRs, mark stories done in sprint-status.yaml and story files, sync GitHub labels, and clean up worktrees and branches. Use when the user invokes the SS menu code in bmad help, or asks to sync BMAD with GitHub, or just merged a PR and wants BMAD updated.
bmad-github-story-create
Sync GitHub state then plan the next story end-to-end via the BMAD create-story flow. Detects blocking dependencies via GitHub labels and updates the GitHub issue label to ready. Use when the user invokes the SC menu code in bmad help, or asks to plan/create the next story, or asks to start the next BMAD story.
bmad-github-story-review
Run BMAD adversarial code review on the current story branch and push fixes. Does NOT mark the story done — the user merges the PR on GitHub. Use when the user invokes the SR menu code in bmad help, or asks to code-review the current story, or asks for an adversarial review of the open story PR.