Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计通过

competitor-monitoring竞争对手监控

Agent Skill

competitor-monitoring 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

34,704

周安装

1,446

GitHub Stars

公开资料未说明

下载量

11,568
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:competitor-monitoring(竞争对手监控)
来源仓库:https://github.com/ivangdavila/competitor-monitoring
安装命令:
openclaw skills install competitor-monitoring
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install competitor-monitoring

简介

competitor-monitoring 跟踪竞争对手定价、功能变化与战略档案,提供预警机制。

  • 适用于电商平台、SaaS 产品或订阅制服务的动态定价与功能迭代监控。
  • 输出包含变更日志、影响评估与应对建议的周期性简报。
  • 使用 openclaw skills install competitor-monitoring 安装,支持自定义监控列表与阈值。
  • 需定期校准监控规则,防止误报或漏报影响决策准确性。

SKILL.md

name
Competitor Monitoring
slug
competitor-monitoring
version
1.0.0
homepage
https://clawic.com/skills/competitor-monitoring
description
Track competitors with pricing alerts, feature changes, positioning analysis, and strategic dossiers.
changelog
Initial release with tracking, alerts, dossiers, and analysis.
metadata
{"clawdbot":{"emoji":"🔍","requires":{"bins":[]},"os":["linux","darwin","win32"]}}

Setup

On first use, read setup.md for integration guidelines.

When to Use

User needs competitive intelligence. Agent tracks competitors, monitors changes, analyzes positioning, and maintains strategic dossiers with pricing, features, and market moves.

Architecture

Memory lives in ~/competitor-monitoring/. See memory-template.md for structure.

~/competitor-monitoring/
├── memory.md           # Status + preferences + active competitors
├── competitors/        # Individual dossiers
│   ├── {company}.md    # Per-competitor intelligence
│   └── ...
├── alerts/             # Triggered alerts
│   └── YYYY-MM-DD.md   # Daily alert log
└── analysis/           # Strategic analyses
    └── {topic}.md      # Comparison reports

Quick Reference

TopicFile
Setup processsetup.md
Memory templatememory-template.md

Core Rules

1. Check Dossiers Before Acting

Before any competitor question, load the relevant competitors/{company}.md file. Build on existing intelligence, don't start fresh each time.

2. Track These Signals

SignalWhere to LookImpact
Pricing changesPricing page, announcementsDirect competitive threat
New featuresChangelog, blog, socialCapability gap/parity
Positioning shiftsHomepage copy, adsMarket narrative
Hiring patternsJobs page, LinkedInStrategic direction
Funding/acquisitionsNews, CrunchbaseResource changes

3. Alert Priorities

  • Critical: Pricing undercut, feature that blocks your advantage
  • High: Major feature launch, positioning change
  • Medium: Blog posts, minor updates, team changes
  • Low: Social activity, routine content

4. Maintain Signal-to-Noise

Don't report everything. Only surface changes that require action or awareness. If nothing actionable happened, say so.

5. Compare Objectively

When analyzing competitors, be honest about their strengths. Acknowledge where they're ahead. False confidence leads to bad strategy.

Framework:

For each competitor, answer honestly:
- Where are they better than us?
- What do their customers love that ours don't have?
- If I were a customer, why would I choose them?

6. Update Dossiers Proactively

After any research or mention of a competitor, update their dossier. Don't wait for explicit instructions.

7. Connect to Strategy

Every observation should connect to "so what?" What does this mean for user's positioning, roadmap, or priorities?

Template:

OBSERVATION: Competitor X launched feature Y
SO WHAT: This means...
→ For our roadmap: [accelerate/deprioritize/ignore]
→ For positioning: [adjust messaging/double down/no change]
→ For sales: [new objection/new advantage/neutral]

Monitoring Patterns

Regular Check-ins

Weekly: Scan pricing pages, homepages, changelogs
Monthly: Deep dive on positioning, feature comparison
Quarterly: Full competitive landscape review

Trigger-Based

  • User mentions competitor → refresh dossier
  • Industry news → check all relevant competitors
  • User launches feature → compare to competitor alternatives

Competitor Dossier Structure

Each competitors/{company}.md contains:

  • Company overview (what they do, target market)
  • Pricing (current, historical changes)
  • Features (core, recent additions)
  • Positioning (messaging, differentiation)
  • Strengths (honest assessment)
  • Weaknesses (opportunities to exploit)
  • Recent moves (last 90 days)
  • Watch list (what to monitor)

Analysis Types

Head-to-Head

Compare user vs one competitor. Feature matrix, pricing, positioning.

User vs Acme Corp:
- Pricing: We're 40% cheaper for same features
- Features: They have X, we have Y (differentiated)
- Positioning: They target enterprise, we target SMB
→ Our wedge: Simpler and cheaper for smaller teams

Landscape

Map all competitors by segment. Who's premium, who's cheap, who's niche.

Market Map (example):
├── Premium ($500+/mo): BigCorp, EnterpriseCo
├── Mid-market ($100-500): CompetitorA, CompetitorB
├── SMB ($20-100): Us, StartupX
└── Free/Freemium: OpenSourceY
→ Gap: No one owns "professional but affordable"

Trend

How is the competitive space evolving? What's the direction?

  • Watch for: New entrants, funding rounds, pivots, acquisitions
  • Pattern recognition: Are competitors moving upmarket? Going vertical?

Gap

Where are opportunities nobody's addressing?

  • Underserved segments
  • Features everyone complains about but nobody fixes
  • Adjacent markets competitors ignore

Common Traps

  • Vanity metrics obsession → Tracking social followers instead of pricing/features. Social numbers don't predict competitive moves.
  • Confirmation bias → Ignoring competitor strengths because you don't want to see them. Honest assessment beats false confidence.
  • Information overload → Reporting every blog post and tweet. Filter for actionable signals, not noise.
  • Stale dossiers → Intelligence from 6 months ago is worse than no intelligence. Update after every mention.
  • Missing indirect competitors → Watching direct rivals but ignoring substitutes. Spreadsheets compete with project management tools.
  • Reactive only → Only checking competitors when something breaks. Proactive monitoring catches threats early.
  • Single source → Only watching their website. Combine: pricing page, changelog, blog, jobs, social, reviews.

Security & Privacy

Data that stays local:

  • All competitor dossiers stored in ~/competitor-monitoring/
  • Analysis reports and alert history
  • User preferences and monitoring settings

What happens on first use:

  • Creates folder ~/competitor-monitoring/ with your data
  • Asks how you want monitoring to work (proactive vs on-demand)

This skill does NOT:

  • Access competitor internal systems
  • Scrape data in violation of ToS
  • Store credentials or sensitive tokens
  • Send your data externally

Related Skills

Install with clawhub install <slug> if user confirms:

  • market-research — broader market analysis
  • business — strategic frameworks
  • analytics — data analysis patterns

Feedback

  • If useful: clawhub star competitor-monitoring
  • Stay updated: clawhub sync

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

72.89%
按下载量换算8,432

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills