Agent skill

competitive-intelligence-monitor

Monitor competitor signals and surface strategic implications for your roadmap. Use when asked to monitor competitors, track the competitive landscape, produce a competitive briefing, or understand what has changed in the market this week or month. Produces a structured intelligence brief with high/medium/low priority signals, roadmap implications, and a strategic landscape summary. For a single competitor announcement use competitor-signal-tracker; for a one-off deep dive use competitor-teardown.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill competitive-intelligence-monitor --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/competitive-intelligence-monitor/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Competitive Intelligence Monitor Skill Turn scattered competitor updates into structured weekly intelligence — not just "what they did" but "what changed since last week and what it means for us." ## Required Inputs Ask the user for these if not provided: - **Competitors to monitor** (list of company names) - **Your current roadmap or strategic priorities** (to assess relevance of signals) - **Previous brief or last run summary** (for diff mode — what's new vs. last time) - **Time period** (this week, this month) ## Signal Categories to Monitor - **Product signals:** New features, removals, UX changes, beta programmes - **Pricing signals:** Changes to tiers, free limits, enterprise terms - **Hiring signals:** Job postings revealing strategic bets - **Partnership signals:** Integrations, acquisitions, ecosystem moves - **Messaging signals:** Changes in positioning, audience, value proposition ## Process ### First Run (Full Report) 1. For each competitor provided, scan all five signal categories 2. Categorise each signal found 3. Assess: reactive (responding to market) or proactive (setting direction)? 4. Rate threat level: High / Medium / Low / Watch 5. Connect each signal to a sp

What's inside
Steps it walks through
  1. Required Inputs
  2. Signal Categories to Monitor
  3. Process
  4. First Run (Full Report)
  5. Subsequent Runs (Diff Only)
  6. Output Structure
  7. Competitive Intelligence Brief — [Date]
  8. Anti-Patterns
  9. Quality Checks
More from pm-claude-skills
All skills →
About this skill
What does the competitive-intelligence-monitor skill do?

Monitor competitor signals and surface strategic implications for your roadmap. Use when asked to monitor competitors, track the competitive landscape, produce a competitive briefing, or understand what has changed in the market this week or month. Produces a structured intelligence brief with high/medium/low priority signals, roadmap implications, and a strategic landscape summary. For a single competitor announcement use competitor-signal-tracker; for a one-off deep dive use competitor-teardown.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill competitive-intelligence-monitor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going