MCPInstall

competitor-monitoring-system

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

Installs
50
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

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

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads competitor-monitoring-system automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

FAQ

What does the competitor-monitoring-system skill do?

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

How do I install competitor-monitoring-system?

Run npx skills add https://github.com/gooseworks-ai/goose-skills --skill competitor-monitoring-system in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/competitor-monitoring-system/ (personal) or .claude/skills/competitor-monitoring-system/ (project).

Which AI agents can use competitor-monitoring-system?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is competitor-monitoring-system safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains competitor-monitoring-system?

It is published by gooseworks-ai in gooseworks-ai/goose-skills. It has 50 recorded installs.

More from gooseworks-ai/goose-skills

View all →

restaurant-booking

gooseworks-ai/goose-skills

Book restaurant reservations via browser automation. Use when asked to make dinner reservations, book a table, or find availability at restaurants. Supports OpenTable, Resy, and direct restaurant booking sites.

send-sms-textbelt

gooseworks-ai/goose-skills

Send SMS text messages to phone numbers. Use when the user asks to send a text, send an SMS, text someone, message a phone number, or send a notification via text message.

245 installs

job-scraper

gooseworks-ai/goose-skills

Search for job postings across LinkedIn and Indeed. Use when users want to find open roles, monitor hiring signals, identify companies hiring for specific positions, or research competitor hiring activity. Returns job title, company, location, salary, description, seniority level, and direct apply URLs. No login or cookies required.

Business & Finance149 installs

linkedin-outreach

gooseworks-ai/goose-skills

End-to-end LinkedIn outreach campaign builder. Takes leads from Supabase, upstream skills, or CSV. Aligns on campaign goal and tone, writes personalized LinkedIn message sequences (connection request + follow-ups + optional InMail), presents for review, and exports for the user's outreach tool (Dripify, Botdog, Expandi, or manual CSV). Logs to Supabase outreachlog.

Marketing & SEO112 installs

find-skill

gooseworks-ai/goose-skills

Find and install skills from the Orthogonal skill library. Use when you need capabilities you don't have, want to discover available skills, or need to add new tools to your agent.

106 installs

linkedin-job-scraper

gooseworks-ai/goose-skills

Scrapes LinkedIn job postings using the JobSpy library (python-jobspy). Use this skill whenever the user wants to find jobs on LinkedIn, search for open roles, pull job listings, build a job pipeline, source job targets for GTM research, or monitor hiring signals. Even if the user just says "find me some jobs" or "what roles is [company] hiring for", use this skill. It runs a local Python script that outputs a CSV of job postings with title, company, location, salary, job type, description, and direct URLs.

Marketing & SEO102 installs

Popular devops & cloud skills

View category →

microsoft-foundry

microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure

OfficialDevOps & Cloud579.1K installs

azure-diagnostics

microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.

OfficialDevOps & Cloud569.8K installs

azure-prepare

microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

OfficialDevOps & Cloud569K installs

azure-ai

microsoft/azure-skills

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.

OfficialDevOps & Cloud568.8K installs

azure-deploy

microsoft/azure-skills

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.

OfficialDevOps & Cloud568.6K installs

azure-validate

microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.

OfficialDevOps & Cloud568K installs