competitor-monitoring

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Competitor Monitoring

竞争对手监测

When to Use

何时使用

Founder wants to know when competitors change pricing, ship features, or raise funding
Founder wants a recurring "what changed this week" scan of competitor activity
Founder wants to detect strategic shifts from competitor job postings, blog posts, or product updates
Founder wants to stay informed without manually checking 10 websites daily

This is the recurring sibling of

competitive-analysis

(one-time deep dive). Use this skill for ongoing monitoring, not initial research.

创始人希望了解竞争对手何时调整价格、发布功能或获得融资
创始人希望定期扫描竞争对手动态，了解“本周有哪些变化”
创始人希望通过竞争对手的招聘信息、博客文章或产品更新发现战略变化
创始人希望及时了解情况，而不必每天手动查看 10 个网站

这是

competitive-analysis

（一次性深度分析）的定期运行姊妹 skill。此 skill 用于持续监测，而非初始调研。

Context Required

所需上下文

List of 3-7 competitors to track (names, websites, product URLs)
What the founder cares about most (pricing, features, positioning, hiring, funding, content)
Monitoring frequency (weekly recommended for early-stage, biweekly for established markets)
The founder's own positioning (to flag threats and opportunities)

需要跟踪的 3-7 个竞争对手列表（名称、网站、产品 URL）
创始人最关注的内容（价格、功能、定位、招聘、融资、内容）
监测频率（早期阶段建议每周一次，成熟市场建议每两周一次）
创始人自身的定位（用于标记威胁和机会）

Workflow

工作流

Define the monitoring surface — for each competitor, identify what to watch:
- Pricing page — plan changes, new tiers, free plan adjustments
- Changelog / release notes — new features, deprecations, platform shifts
- Job postings — engineering roles signal product direction, sales roles signal GTM shifts, exec hires signal strategy changes
- Blog / content — new positioning, case studies (reveal target customers), thought leadership pivots
- Social media — founder posts, company announcements, community reactions
- Review sites — new reviews on G2, Capterra, Trustpilot (sentiment shifts)
- Funding / press — Crunchbase alerts, press releases, media coverage
Set up the monitoring stack — recommend tools and manual checks:
- Automated: Google Alerts (brand mentions), Visualping or ChangeTower (page change detection), Crunchbase alerts (funding), LinkedIn job alerts
- Manual weekly scan: pricing pages, changelogs, recent blog posts, latest job postings
- Quarterly deep dive: full
```
competitive-analysis
```
  refresh
Run the scan — check all sources for the monitoring period and flag changes.
Analyze signals — for each change detected:
- What changed (factual description)
- What it signals (interpretation — are they moving upmarket? entering your segment? struggling with churn?)
- Threat level (none / watch / respond / urgent)
- Recommended action (if any)
Generate the report — produce a concise weekly/biweekly competitor intel brief.

定义监测范围——为每个竞争对手确定需要关注的内容：
- 定价页面——套餐变化、新增层级、免费版调整
- 更新日志 / 发布说明——新功能、功能弃用、平台调整
- 招聘信息——工程岗位表明产品方向，销售岗位表明 GTM 变化，高管招聘表明战略变化
- 博客 / 内容——新的市场定位、客户案例（揭示目标客户）、思想领导力方向转变
- 社交媒体——创始人动态、公司公告、社区反馈
- 评论平台——G2、Capterra、Trustpilot 上的新评论（情感趋势变化）
- 融资 / 新闻——Crunchbase 提醒、新闻稿、媒体报道
建立监测工具栈——推荐相关工具和手动检查方式：
- 自动化： Google Alerts（品牌提及）、Visualping 或 ChangeTower（页面变更检测）、Crunchbase 提醒（融资）、LinkedIn 职位提醒
- 每周手动扫描： 定价页面、更新日志、最新博客文章、最新招聘信息
- 每季度深度分析： 全面刷新
```
competitive-analysis
```
执行扫描——检查监测周期内的所有信息来源，并标记变化。
分析信号——针对每个检测到的变化：
- 发生了什么（事实描述）
- 这释放了什么信号（解读——他们是否正在向高端市场拓展？是否进入你的细分市场？是否正在面临用户流失问题？）
- 威胁等级（无 / 关注 / 应对 / 紧急）
- 建议行动（如有）
生成报告——制作一份简洁的每周或双周竞争对手情报简报。

Output Format

输出格式

markdown

undefined

markdown

undefined

Competitor Intel Brief — Week of [Date]

竞争对手情报简报 — [日期]所在周

Summary

摘要

[1-2 sentence overview: "Quiet week. Competitor A shipped a free tier. No pricing changes elsewhere."]

[用 1-2 句话概述：“本周较为平静。竞争对手 A 发布了免费版。其他竞争对手没有价格变化。”]

Changes Detected

检测到的变化

[Competitor A]

What changed: [factual description]
Signal: [what this likely means strategically]
Threat level: [None / Watch / Respond / Urgent]
Recommended action: [what to do, if anything]

[Competitor B]

No changes detected this period.

[竞争对手 A]

发生了什么： [事实描述]
信号： [这在战略上可能意味着什么]
威胁等级： [无 / 关注 / 应对 / 紧急]
建议行动： [如有必要，应采取什么行动]

[竞争对手 B]

本监测周期内未检测到变化。

Job Posting Signals

招聘信息信号

Competitor	New Roles	Signal
[A]	3 enterprise AEs, VP Sales	Moving upmarket
[B]	ML engineer, data scientist	Building AI features

竞争对手	新增职位	信号
[A]	3 个企业级 AE、销售副总裁	向高端市场拓展
[B]	ML 工程师、数据科学家	正在构建 AI 功能

Emerging Patterns

新出现的趋势

[Pattern observed across multiple competitors or over time]

[在多个竞争对手之间或随时间观察到的趋势]

Action Items

行动项

[Specific action for the founder]

undefined

[创始人需要采取的具体行动]

undefined

Frameworks & Best Practices

框架与最佳实践

Reading job postings as strategy signals:

Role Type	What It Signals
Enterprise AEs / Sales Engineers	Moving upmarket or launching enterprise tier
DevRel / Community Manager	Investing in developer ecosystem or community-led growth
ML/AI Engineers	Building AI features or data products
International roles / specific geo	Expanding to new markets
Product Marketing Manager	Repositioning or launching new product lines
Head of Partnerships	Platform/ecosystem strategy
Lots of support hires	Scaling fast or struggling with quality

Threat level framework:

None: Routine activity, no impact on you
Watch: Interesting move, could affect you in 3-6 months — add to next strategy discussion
Respond: Directly affects your positioning, pricing, or target market — needs a plan within 2 weeks
Urgent: Launches directly competing feature, undercuts your pricing, or targets your exact ICP — needs immediate response

Common mistakes:

Monitoring too many competitors (pick 3-5, not 15)
Reacting to every move instead of identifying patterns
Confusing competitor activity with competitor success (they shipped a feature — doesn't mean it works)
Ignoring indirect competitors and new entrants
Not archiving snapshots (you'll want to see how their pricing page looked 6 months ago)

将招聘信息作为战略信号来解读：

职位类型	释放的信号
企业级 AE / 售前工程师	向高端市场拓展或推出企业版
DevRel / 社区经理	投入开发者生态或采用社区驱动的增长策略
ML/AI 工程师	正在构建 AI 功能或数据产品
国际化岗位 / 特定地区岗位	扩展到新市场
产品营销经理	重新定位或推出新产品线
合作负责人	平台 / 生态战略
大量招聘支持岗位	快速扩张或服务质量承压

威胁等级框架：

无：日常活动，不会对你造成影响
关注： 出现了值得注意的动向，可能在 3-6 个月内影响你——加入下一次战略讨论
应对： 直接影响你的定位、定价或目标市场——需要在 2 周内制定应对计划
紧急： 发布了直接竞争的功能、低价抢客，或瞄准了你的 Exact ICP——需要立即响应

常见错误：

监测过多竞争对手（选择 3-5 个，而不是 15 个）
对每一步行动都立即作出反应，而不是识别趋势
混淆竞争对手的动作与竞争对手的成功（他们发布了某个功能——并不意味着该功能有效）
忽视间接竞争对手和新进入者
不保存历史快照（你可能需要查看他们 6 个月前的定价页面是什么样子）

Related Skills

Examples

示例

Prompt: "Set up competitor monitoring for our 4 main competitors in the email marketing space."

Good output includes: Monitoring surface for each competitor (pricing pages, changelogs, job boards, blogs), recommended tool stack for automated alerts, and a template for the weekly intel brief.

Prompt: "What have our competitors been up to this week?"

Good output includes: Scan of changelogs, pricing pages, blog posts, job postings, and social accounts for each tracked competitor. Flagged changes with signal interpretation and threat levels. Actionable summary.

提示词：“为我们在电子邮件营销领域的 4 个主要竞争对手设置竞争对手监测。”

良好输出包括： 为每个竞争对手制定监测范围（定价页面、更新日志、招聘网站、博客）、用于自动预警的推荐工具栈，以及每周情报简报模板。

提示词：“我们的竞争对手本周都有哪些动态？”

良好输出包括： 扫描每个受监测竞争对手的更新日志、定价页面、博客文章、招聘信息和社交账号。标记发生变化的内容，并提供信号解读、威胁等级和可执行的摘要。