Token导航 LogoToken导航

Agent Skill · 研究检索

competitor-monitoring(竞争对手监控)

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

competitor-monitoring 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 4,214。

总安装 34,704周安装 1,446GitHub Stars 公开资料未说明下载 11,568核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

competitor-monitoring 跟踪竞争对手定价、功能变化与战略档案,提供预警机制。适用于电商平台、SaaS 产品或订阅制服务的动态定价与功能迭代监控。输出包含变更日志、影响评估与应对建议的周期性简报。

使用 openclaw skills install competitor-monitoring 安装,支持自定义监控列表与阈值。需定期校准监控规则,防止误报或漏报影响决策准确性。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install competitor-monitoring;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

competitor-monitoring 怎么安装?

在终端执行 openclaw skills install competitor-monitoring。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

competitor-monitoring 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

competitor-monitoring 需要什么权限?

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

competitor-monitoring 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

competitor-monitoring 用的人多吗?

公开数据是累计安装 34,704 次,近一周安装 1,446 次,下载 11,568 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

competitor-monitoring 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
competitor-monitoring

竞争对手监控 · 本页

34,704—需要联网MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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

平台分布

OpenClaw

72.89%
按下载量换算8,432

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills