Ongoing Competitive Monitoring

Competitor monitoring system

by gooseworks-ai · MIT license · ★ 1,220 on GitHub · updated Sep 21

Set up and run ongoing competitive intelligence monitoring for a client. Tracks competitor content, ads, reviews, social, and product moves.

---
type: playbook
name: competitor-monitoring-system
description: >
  Set up and run ongoing competitive intelligence monitoring for a client.
  Tracks competitor content, ads, reviews, social, and product moves.
---

# 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"

Overview

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

Manual install (npx, ZIP)

Claude Codenpx skills add gooseworks-ai/goose-skills --skill competitor-monitoring-system -g -a claude-code

Claude Code (manual)

mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/gooseworks-ai/goose-skills/tar.gz/615c685f34f8 \
  | tar -xz -C ~/.claude/skills --strip-components=4 goose-skills-615c685f34f8/skills/competitive-intel/playbooks/competitor-monitoring-system

Windows (PowerShell)

New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/3a17627073e4087ea7dc/competitor-monitoring-system.zip" -OutFile "$env:TEMP\competitor-monitoring-system.zip"; Expand-Archive "$env:TEMP\competitor-monitoring-system.zip" -DestinationPath "$HOME\.claude\skills" -Force

Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md3.9 KB
skill.meta.json285 B

Read the files here

gooseworks-ai/615c6852 files

SKILL.md

Show the full text109 lines

competitor-monitoring-system/SKILL.md109 lines · 3.9 KB

PreviewCode

Outline

RawView on GitHub

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 Monitor	Frequency	Skill	What to Look For
Blog/content output	Weekly	blog-feed-monitor	New posts, topic shifts, SEO attacks
Social media posts	Weekly	linkedin-profile-post-scraper + twitter-mention-tracker	Messaging changes, product announcements, engagement patterns
Reddit/HN mentions	Weekly	reddit-post-finder + hacker-news-scraper	User sentiment, complaints, praise, feature requests
Ad creative changes	Bi-weekly	google-ad-scraper + web_search (Meta Ad Library)	New campaigns, messaging shifts, spend changes
Review sentiment	Monthly	review-site-scraper	New reviews, rating trends, common complaints

4. Run Monitoring

Each monitoring cycle:

Run the relevant scrapers for the cycle type
Compare new data against the baseline/previous cycle
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

1	---
2	type: playbook
3	name: competitor-monitoring-system
4	description: >
5	Set up and run ongoing competitive intelligence monitoring for a client.
6	Tracks competitor content, ads, reviews, social, and product moves.
7	---
8
9	# Competitor Monitoring System
10
11	Set up ongoing competitive intelligence for a client. Monitor competitor content, ads, reviews, social presence, and product moves. Produce regular intelligence reports.
12
13	## When to Use
14
15	- "Set up competitor monitoring for [client]"
16	- "Track what [competitors] are doing"
17	- "Monitor [competitor] content and ads"
18
19	## Prerequisites
20
21	- List of competitors to track (typically 3-7)
22	- Client context with competitive positioning
23	- Competitor founder/executive LinkedIn profiles (for social monitoring)
24
25	## Setup Steps
26
27	### 1. Define Competitor Watchlist
28
29	Create a competitor tracking file: `clients/<client-name>/intelligence/competitor-watchlist.md`
30
31	For each competitor, document:
32	- Company name and URL
33	- Key products/features
34	- Founder/exec LinkedIn profiles
35	- Known content channels (blog URL, YouTube, podcast)
36	- Review profiles (G2, Capterra URLs)
37	- Ad library pages (Meta, Google)
38
39	### 2. Initial Competitive Baseline
40
41	Run the full competitor-intel composite for each competitor to establish a baseline:
42
43	Skill: competitor-intel (chains reddit + twitter + linkedin + blog + review scrapers)
44
45	Plus:
46	- Skill: google-ad-scraper — Scrape their current Google ads
47	- Method: Use `web_search` against Meta Ad Library (facebook.com/ads/library) for Meta ad research
48	- Skill: review-site-scraper — Pull latest G2/Capterra/Trustpilot reviews
49
50	Output: `clients/<client-name>/intelligence/competitor-baseline.md`
51
52	### 3. Configure Monitoring Cadence
53
54	\| What to Monitor \| Frequency \| Skill \| What to Look For \|
55	\|----------------\|-----------\|-------\|-----------------\|
56	\| Blog/content output \| Weekly \| blog-feed-monitor \| New posts, topic shifts, SEO attacks \|
57	\| Social media posts \| Weekly \| linkedin-profile-post-scraper + twitter-mention-tracker \| Messaging changes, product announcements, engagement patterns \|
58	\| Reddit/HN mentions \| Weekly \| reddit-post-finder + hacker-news-scraper \| User sentiment, complaints, praise, feature requests \|
59	\| Ad creative changes \| Bi-weekly \| google-ad-scraper + web_search (Meta Ad Library) \| New campaigns, messaging shifts, spend changes \|
60	\| Review sentiment \| Monthly \| review-site-scraper \| New reviews, rating trends, common complaints \|
61
62	### 4. Run Monitoring
63
64	Each monitoring cycle:
65
66	1. Run the relevant scrapers for the cycle type
67	2. Compare new data against the baseline/previous cycle
68	3. Flag significant changes:
69	- New product features or pricing changes
70	- New content targeting our client's keywords
71	- Negative review trends (poaching opportunity)
72	- New ad campaigns (messaging intelligence)
73	- Founder/exec public statements about strategy
74
75	### 5. Produce Intelligence Report
76
77	After each cycle, produce a brief intelligence summary:
78
79	```
80	# Competitor Intelligence — [Client] — Week of [Date]
81
82	## Key Changes
83	- [Competitor A] published 3 new blog posts targeting "[keyword]"
84	- [Competitor B] launched new Meta ad campaign focused on [theme]
85	- [Competitor C] received 5 negative G2 reviews about [issue]
86
87	## Recommended Actions
88	- Publish response content for [Competitor A]'s keyword attack
89	- Create comparison page addressing [Competitor B]'s new messaging
90	- Target [Competitor C]'s unhappy customers with migration content
91
92	## Detailed Findings
93	[Per-competitor breakdown]
94	```
95
96	Output: `clients/<client-name>/intelligence/competitor-reports/[date].md`
97
98	## Ongoing Cadence
99
100	- Weekly: Content + social monitoring, brief report
101	- Bi-weekly: Ad monitoring
102	- Monthly: Full review scrape + comprehensive report
103	- Quarterly: Re-run full competitor-intel baseline, update watchlist
104
105	## Human Checkpoints
106
107	- After setup: Review competitor watchlist and monitoring plan
108	- After each report: Review recommended actions before executing
109