competitor-intel

Competitor intelligence system. Track competitors across Reddit, Twitter/X, and LinkedIn. Run one-time deep research to create competitor profiles, then automate daily/weekly monitoring with consolidated reports and actionable signals. Reports delivered as markdown files and via email.

381 stars

Best use case

competitor-intel is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Competitor intelligence system. Track competitors across Reddit, Twitter/X, and LinkedIn. Run one-time deep research to create competitor profiles, then automate daily/weekly monitoring with consolidated reports and actionable signals. Reports delivered as markdown files and via email.

Teams using competitor-intel should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/competitor-intel/SKILL.md --create-dirs "https://raw.githubusercontent.com/gooseworks-ai/goose-skills/main/skills/composites/competitor-intel/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/competitor-intel/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How competitor-intel Compares

Feature / Agentcompetitor-intelStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Competitor intelligence system. Track competitors across Reddit, Twitter/X, and LinkedIn. Run one-time deep research to create competitor profiles, then automate daily/weekly monitoring with consolidated reports and actionable signals. Reports delivered as markdown files and via email.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Competitor Intelligence

Automated competitor monitoring and intelligence gathering system.

**Important:** Before running any competitor intel commands, ask the user which competitors they want to track. Do not assume or hardcode competitor names.

## Quick Start

### One-Time: Research a New Competitor

```bash
# Create a new competitor profile (agent-driven research)
python3 competitor-intel/scripts/setup_competitor.py --name "CompanyName" --website https://example.com --slug companyname
```

Then run an agent research session to populate the profile.

### Daily: Reddit + Twitter Monitoring

```bash
# Run daily signals collection (automated via cron)
python3 competitor-intel/scripts/run_daily.py

# Or for a specific competitor
python3 competitor-intel/scripts/run_daily.py --competitor <competitor-slug>
```

### Weekly: Deep Dive + LinkedIn

```bash
# Run weekly deep dive (Monday mornings)
python3 competitor-intel/scripts/run_weekly.py
```

### Generate Report

```bash
# Generate daily or weekly report
python3 competitor-intel/scripts/generate_report.py --type daily --date 2026-02-21
python3 competitor-intel/scripts/generate_report.py --type weekly --date 2026-02-21
```

## Data Structure

- `competitor-intel/competitors/[slug]/profile.md` - Deep research profile per competitor
- `competitor-intel/competitors/[slug]/snapshots/` - Point-in-time weekly snapshots
- `competitor-intel/reports/` - Daily and weekly digest reports
- `competitor-intel/raw-data/` - Raw JSON from Reddit/Twitter scrapes
- `competitor-intel/config.json` - Global configuration

## Tracked Competitors

Competitors are configured per-project. Ask the user which competitors to track, then add them here:

| Competitor | Slug | Status |
|---|---|---|
| *(ask user)* | — | — |

## Automation

- **Daily (8 AM PT)**: Reddit + Twitter scrape → daily report → email
- **Weekly (Monday 9 AM PT)**: Deep dive + LinkedIn + weekly report → email

## Dependencies

- Apify API (Reddit + Twitter scraping) - token in config.json
- Web search (LinkedIn founder tracking, one-time research)
- AgentMail (report delivery)

Related Skills

competitor-monitoring-system

381
from gooseworks-ai/goose-skills

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

competitor-signals

381
from gooseworks-ai/goose-skills

Extract leads from competitor product activity — Product Hunt commenters/upvoters, HN posts about competitors, case studies, testimonials, tech press, and switching signals. Detects people actively switching from competitors as highest-priority leads.

review-intelligence-digest

381
from gooseworks-ai/goose-skills

Scrape G2, Capterra, and Trustpilot reviews for your product and competitors, then extract recurring themes, objections, proof points, and exact customer language for use in messaging. Chains review-scraper with LLM analysis. Produces a weekly or monthly digest that feeds directly into copywriting, positioning, and sales enablement. Use when a marketing team needs to ground messaging in real customer language.

competitor-content-tracker

381
from gooseworks-ai/goose-skills

Monitor competitor content across blogs, LinkedIn, and Twitter/X on a recurring basis. Surfaces new posts, trending topics, and content gaps you can own. Chains blog-scraper, linkedin-profile-post-scraper, and twitter-scraper. Use when you want a weekly digest of what competitors are publishing and which topics are generating engagement.

competitor-ad-teardown

381
from gooseworks-ai/goose-skills

Deep-dive analysis of a competitor's ad strategy. Scrapes their Meta + Google ads, reverse-engineers their funnel (ad → landing page → CTA), identifies positioning bets, and produces a strategic teardown. Goes beyond ad-creative-intelligence by analyzing the full conversion path and strategic intent behind each campaign.

competitive-pricing-intel

381
from gooseworks-ai/goose-skills

Monitor competitor pricing pages via live web scrape and Web Archive snapshots. Track plan changes, tier restructuring, new pricing models, and feature gating shifts. Produces a pricing comparison matrix and flags when a competitor changes packaging. Use when a product marketing team needs to stay current on competitive pricing or when preparing for a pricing change of their own.

ad-creative-intelligence

381
from gooseworks-ai/goose-skills

Scrape competitor ads from Meta and Google ad libraries, cluster by hook/angle/format, and surface new creative directions your team hasn't tested. Chains meta-ad-scraper and google-ad-scraper. Use when a marketing team wants to understand the competitive ad landscape before launching a campaign, or wants fresh creative inspiration from what's already working in the market.

orthogonal-competitor-research

380
from gooseworks-ai/goose-skills

Research competitors - products, pricing, team, funding, and strategy

orthogonal-company-intel

380
from gooseworks-ai/goose-skills

Full company intelligence report - overview, team, funding, products, news

landing-page-intel

380
from gooseworks-ai/goose-skills

Extract competitor and customer intelligence from any company's landing page HTML. Discovers tech stack, analytics tools, ad pixels, customer logos, SEO metadata, CTAs, hidden elements, and more. No API keys required.

competitor-post-engagers

380
from gooseworks-ai/goose-skills

Find leads by scraping engagers from a competitor's top LinkedIn posts. Given one or more company page URLs, scrapes recent posts, ranks by engagement, selects the top N, extracts all reactors and commenters, ICP-classifies, and exports CSV. Use when someone wants to "find leads engaging with competitor content" or "scrape people who interact with [company]'s LinkedIn posts".

signal-detection-pipeline

381
from gooseworks-ai/goose-skills

Detect buying signals from multiple sources, qualify leads, and generate outreach context