competitor-analysis
Deep competitive analysis + ongoing monitoring. Checks user research for competitor mentions, sales notes, existing analysis. Integrates with retention-analysis and user-research-synthesis.
npx skills add majiayu000/claude-skill-registry --skill competitor-analysis-timothynguyen04-pmos --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill provides two modes: Deep Analysis (a comprehensive one-time research) and Ongoing Monitoring (regular, periodic tracking). It scans internal workspace data (user research, meetings, PRDs, strategy, metrics) to surface existing intelligence, identify gaps, and fill them with web research. It outputs a strategic report detailing defensive, offensive, and innovative plays, with a format path shown for outputs. It also integrates with other skills (retention-analysis, user-research-synthesis) and supports cross-skill workflow, including linking to battlecards and roadmap updates.
How it works
- It prompts for competitor names and mode selection (Deep Analysis or Ongoing Monitoring).
- It checks internal sources:
context-library/research/,context-library/research/competitive-*.md,context-library/meetings/,context-library/prds/,context-library/strategy/, andcontext-library/metrics/for relevant intelligence. - If analytics MCP is connected, it may query churn data from Amplitude/Mixpanel.
- It aggregates internal intelligence, highlights gaps, then conducts web research to fill gaps.
- It produces outputs such as a comprehensive report (Deep Analysis) or monthly competitive intel updates (Ongoing Monitoring) and saves them to paths like
outputs/research-synthesis/competitor-analysis-[date].mdoroutputs/research-synthesis/competitive-intel-[month].md. - It suggests cross-skill references and how the findings should inform PRDs, product strategy, retention, and user research.
When to use it
Use Deep Analysis when entering a new market, launching major features, or preparing strategic decisions (roadmap, pricing, positioning). Use Ongoing Monitoring when you already have baseline intel and want regular updates (monthly check-ins).
What it can touch
The skill integrates with other workstreams and outputs, including:
- Cross-Skill Integration: informs
/prd-draft,/write-prod-strategy,/retention-analysis,/user-research-synthesis. - Output files:
outputs/research-synthesis/competitor-analysis-[name]-[date].md(Deep Analysis) oroutputs/research-synthesis/competitive-intel-[month].md(Ongoing Monitoring).
Caveats
The skill relies on internal context first; web research is intended only to fill gaps not covered by internal data. It requires precise competitor names and mode choice to function properly. No outcomes are promised beyond the stated outputs and process; internal intelligence must exist or be generated via the described steps. License and provenance notes are not part of the operational review.
# /competitor-analysis - Strategic Competitive Intelligence Two modes: **Deep Analysis** (comprehensive one-time research) + **Ongoing Monitoring** (weekly/monthly tracking) ## Quick Start 1. Name the competitor(s) you want to analyze 2. Choose mode: **Deep Analysis** (full research) or **Ongoing Monitoring** (monthly check-in) 3. I check your workspace first -- user research, meeting notes, churn data, past analysis 4. I show what we already know, identify gaps, then fill gaps with web research 5. I deliver a strategic report with defensive, offensive, and innovative plays **Example:** "Analyze Competitor X -- we're losing enterprise deals to them" **Output:** `outputs/research-synthesis/competitor-analysis-[name]-[date].md` **Time:** Deep Analysis: 2-4 hours | Monitoring: 30 min/month ## Context Routing Logic (Internal - for Claude) **Automatic Context Checks:** When this skill is invoked, immediately check: | Source | Files/Folders | Search Terms | What to Extract | |--------|---------------|--------------|-----------------| | User Research | `context-library/research/*.md` | competitor name, "switched to", "chose", "vs [competitor]", "competitor" | Customer quotes, pain points,
- Quick Start
- Context Routing Logic (Internal - for Claude)
- Step 0: Understanding What We Already Know
- Internal Intelligence Summary
- Gaps in Knowledge
- Step 1: Choose Your Analysis Mode
- Deep Analysis Mode
- Ongoing Monitoring Mode
- Deep Analysis Mode: PM-Specific Questions
- Question 1: Competitive Context
- Question 2: Customer Segment
- Question 3: Churn Reasons
- Question 4: Distribution Advantage
- Question 5: Lost Segments
What does the competitor-analysis skill do?
Deep competitive analysis + ongoing monitoring. Checks user research for competitor mentions, sales notes, existing analysis. Integrates with retention-analysis and user-research-synthesis.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill competitor-analysis-timothynguyen04-pmos --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 majiayu000/claude-skill-registry, a repository with 534 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.