Token导航 LogoToken导航TokenDH.com
研究检索权限需确认github未标认证来源可访问许可证需确认审计提醒

competitor-monitoring-system竞争对手监控系统

Agent Skill

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

总安装

196

周安装

8

GitHub Stars

630

下载量

63
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/gooseworks-ai/goose-skills --skill competitor-monitoring-system

简介

为特定客户定制专属监控方案覆盖内容广告评价社交全链条跟踪。

  • 自动生成定期简报同步最新动作与战略意图推断结果。
  • 支持多项目并行管理并通过配置文件隔离不同客户数据资产。
  • 必须准备完整的竞争对手列表与客户背景资料包才能开展部署工作。
  • competitor-monitoring-system 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Competitor Monitoring System

Set up ongoing competitive intelligence for a client. Monitor competitor content, ads, reviews, social presence, and product moves. Produce regular intelligence reports.

When to Use

  • "Set up competitor monitoring for [client]"
  • "Track what [competitors] are doing"
  • "Monitor [competitor] content and ads"

Prerequisites

  • List of competitors to track (typically 3-7)
  • Client context with competitive positioning
  • Competitor founder/executive LinkedIn profiles (for social monitoring)

Setup Steps

1. Define Competitor Watchlist

Create a competitor tracking file: clients/<client-name>/intelligence/competitor-watchlist.md

For each competitor, document:

  • Company name and URL
  • Key products/features
  • Founder/exec LinkedIn profiles
  • Known content channels (blog URL, YouTube, podcast)
  • Review profiles (G2, Capterra URLs)
  • Ad library pages (Meta, Google)

2. Initial Competitive Baseline

Run the full competitor-intel composite for each competitor to establish a baseline:

Skill: competitor-intel (chains reddit + twitter + linkedin + blog + review scrapers)

Plus:

  • Skill: google-ad-scraper — Scrape their current Google ads
  • Method: Use web_search against Meta Ad Library (facebook.com/ads/library) for Meta ad research
  • Skill: review-site-scraper — Pull latest G2/Capterra/Trustpilot reviews

Output: clients/<client-name>/intelligence/competitor-baseline.md

3. Configure Monitoring Cadence

What to MonitorFrequencySkillWhat to Look For
Blog/content outputWeeklyblog-feed-monitorNew posts, topic shifts, SEO attacks
Social media postsWeeklylinkedin-profile-post-scraper + twitter-mention-trackerMessaging changes, product announcements, engagement patterns
Reddit/HN mentionsWeeklyreddit-post-finder + hacker-news-scraperUser sentiment, complaints, praise, feature requests
Ad creative changesBi-weeklygoogle-ad-scraper + web_search (Meta Ad Library)New campaigns, messaging shifts, spend changes
Review sentimentMonthlyreview-site-scraperNew reviews, rating trends, common complaints

4. Run Monitoring

Each monitoring cycle:

  1. Run the relevant scrapers for the cycle type
  2. Compare new data against the baseline/previous cycle
  3. Flag significant changes:

- New product features or pricing changes - New content targeting our client's keywords - Negative review trends (poaching opportunity) - New ad campaigns (messaging intelligence) - Founder/exec public statements about strategy

5. Produce Intelligence Report

After each cycle, produce a brief intelligence summary:

# Competitor Intelligence — [Client] — Week of [Date]

## Key Changes
- [Competitor A] published 3 new blog posts targeting "[keyword]"
- [Competitor B] launched new Meta ad campaign focused on [theme]
- [Competitor C] received 5 negative G2 reviews about [issue]

## Recommended Actions
- Publish response content for [Competitor A]'s keyword attack
- Create comparison page addressing [Competitor B]'s new messaging
- Target [Competitor C]'s unhappy customers with migration content

## Detailed Findings
[Per-competitor breakdown]

Output: clients/<client-name>/intelligence/competitor-reports/[date].md

Ongoing Cadence

  • Weekly: Content + social monitoring, brief report
  • Bi-weekly: Ad monitoring
  • Monthly: Full review scrape + comprehensive report
  • Quarterly: Re-run full competitor-intel baseline, update watchlist

Human Checkpoints

  • After setup: Review competitor watchlist and monitoring plan
  • After each report: Review recommended actions before executing

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

36.21%
按下载量换算23

Claude

28.06%
按下载量换算18

Cursor

18.11%
按下载量换算11

Gemini CLI

9.01%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

可疑

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

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

来源信息

继续浏览同类 Skills