Competitive Analysis Skill

Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations.

Competitive Analysis Skill — The Skill Playground: pick the Executive Update skill, fill in a few notes, hit run, and watch a structured executive… (from the mohitagw15856/pm-claude-skills README)

From the mohitagw15856/pm-claude-skills README — shows the whole collection, not only this skill. · view on GitHub

How to use it

Claude Code
  1. Run the line below. It pulls the whole folder into ~/.claude/skills/competitive-analysis.
  2. Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit mohitagw15856/pm-claude-skills/skills/competitive-analysis#main ~/.claude/skills/competitive-analysis

For one project only, change the path to .claude/skills/competitive-analysis.

Claude (web or desktop app)
  1. On this page open ⋯ → Download .md.
  2. Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
  3. Pick the file and Save. Claude shows the name and description and runs a security scan.
  4. Check the skill is switched on.
  5. Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
  1. ChatGPT: make a Project and paste it into Instructions.
  2. Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Source of Competitive Analysis Skill

Show the full text126 lines
namedescription
competitive-analysisAnalyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations. For a one-off teardown of a single rival use competitor-teardown; for a recurring market briefing use competitive-intelligence-monitor.

Competitive Analysis Skill

Create structured competitive analyses for product decision-making.

Reads from / Writes to the Brain

If a professional-brain (brain/) exists, ground in it instead of re-asking for what you already know:

  • Read first: knowledge/ (market + positioning) and competitor entities/. Run python3 ../professional-brain/scripts/brain_query.py ./brain "<competitor or market>" and carry each fact's provenance tag through — a competitor claim from a press release is [external], not [data].
  • 📥 Propose to the Brain: after producing, propose recording new competitor facts to knowledge/ ([external]) and creating/updating competitor entities/. Show them, get a yes, then write with ../professional-brain/scripts/brain_write.py … --commit (append-only, dry-run by default).

Required Inputs

Ask the user for these if not provided:

  • Your product or company (what you're comparing against)
  • Competitors to analyze (or ask to identify the top 3-5)
  • Analysis focus (full landscape / feature comparison / pricing / positioning / win-loss)
  • Audience (product team / leadership / sales / board)

Process

  1. Gather competitor information from provided inputs and available context
  2. Build profiles for each competitor
  3. Create feature comparison matrix on dimensions that matter to the user's customers
  4. Analyze pricing and positioning
  5. Identify win/loss patterns and strategic implications
  6. Validate — Confirm all claims reference a specific source or are flagged as assumptions. Verify feature comparisons note quality differences, not just presence/absence.

Output Structure

1. Executive Summary
  • Market Position: Where we stand relative to competitors
  • Key Findings: Top 3-5 insights
  • Strategic Implications: What this means for the roadmap
2. Competitor Profiles

For each competitor:

  • Company Overview: Size, funding, market position
  • Target Customer: Who they serve
  • Value Proposition: Core positioning
  • Strengths / Weaknesses: What they do well and where they fall short
  • Recent Activity: Major updates, funding, announcements
3. Feature Comparison Matrix
Feature Us Competitor A Competitor B Competitor C
[Feature] ✅ Full ⚠️ Limited ❌ None ✅ Full

Legend: ✅ Full (production-ready) · ⚠️ Limited/Beta · ❌ None

Include notes on quality and implementation differences where significant.

4. Pricing Comparison
Plan Us Competitor A Competitor B
Free/Trial [price] [price] [price]
Pro [price] [price] [price]
Enterprise [price] [price] [price]
5. Market Positioning Map

Position competitors on two key dimensions relevant to the market:

  • Y-Axis: [e.g., Enterprise vs. SMB]
  • X-Axis: [e.g., Simple vs. Comprehensive]

Whitespace Opportunities: [Underserved segments]

6. Win/Loss Analysis

Why We Win:

  • Better at: [specific capabilities]
  • Customers who value: [what matters to them]

Why We Lose:

  • When customers need: [specific requirements]
  • Their advantage: [what tips the decision]
7. Strategic Recommendations

Immediate Actions (0-3 months):

  1. [Action] — [Rationale]

Medium-term (3-12 months):

  1. [Action] — [Rationale]

Anti-Patterns

  • Do not present competitor feature claims as facts without citing a source or flagging them as assumptions — outdated or incorrect feature data misleads sales and product decisions
  • Do not build a competitive analysis that only covers features — pricing, messaging, go-to-market motion, and who they hire for are equally strategic signals
  • Do not treat all buyers as identical — the same product may win against Competitor A in the enterprise segment and lose in SMB; segment-specific win/loss matters
  • Do not soften weaknesses and threats in the SWOT to avoid internal discomfort — an honest SWOT is only useful if the negatives are real

Deeper Materials

This skill ships with support files — use them when they are available:

  • references/feature-matrix-honesty.md — Feature Matrices That Don't Lie. Apply it while producing the output; it carries the calibration and judgment calls the method summary above compresses.
  • templates/landscape-doc.md — a fill-in version of the deliverable with the quality gates inline. Offer it when the user wants to work the document themselves rather than have it generated.

Scoring Rubric (0–40)

Score any output of this skill before handing it over; 32+ is ship-quality.

Dimension 0 5 10
Source hygiene Competitor claims stated as fact with no provenance; stale data presented as current Major claims sourced, but assumptions unflagged and mixed in with verified facts Every claim carries a source tag or explicit assumption flag; an assumption register tells the reader what to re-verify
Depth beyond the feature checklist A feature matrix and nothing else Features plus pricing, but no positioning, GTM motion, or recent-moves analysis Features, pricing, positioning map, and win/loss all present — with quality-difference notes where checkmark parity would mislead
Segment-aware win/loss One generic strengths/weaknesses list averaged across all buyers Win/loss present but undifferentiated by segment or based on internal opinion, not customer evidence Win/loss split by segment with customer-voiced reasons and deal counts; contradicting segments (win SMB, lose enterprise) shown side by side
Actionability of recommendations Generic advice ("monitor competitors", "improve differentiation") Directionally useful actions but untethered from the findings or missing timeframes Specific actions with timeframe and rationale, each traceable to a numbered finding — including explicit non-actions

Quality Checks

  • All competitor claims cite a source or are flagged as assumptions
  • Feature comparison notes quality differences, not just feature presence
  • Strategic recommendations are specific actions, not generic advice
  • Win/loss analysis reflects customer perspective, not internal assumptions
  • Different customer segments are considered (not all buyers value the same things)
1---
2name: competitive-analysis
3description: "Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations. For a one-off teardown of a single rival use competitor-teardown; for a recurring market briefing use competitive-intelligence-monitor."
4---
5 
6# Competitive Analysis Skill
7 
8Create structured competitive analyses for product decision-making.
9 
10## Reads from / Writes to the Brain
11 
12If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, ground in it instead of re-asking for what you already know:
13 
14- **Read first:** `knowledge/` (market + positioning) and competitor `entities/`. Run `python3 ../professional-brain/scripts/brain_query.py ./brain "<competitor or market>"` and carry each fact's provenance tag through — a competitor claim from a press release is `[external]`, not `[data]`.
15- **📥 Propose to the Brain:** after producing, propose recording new competitor facts to `knowledge/` (`[external]`) and creating/updating competitor `entities/`. Show them, get a yes, then write with `../professional-brain/scripts/brain_write.py … --commit` (append-only, dry-run by default).
16 
17## Required Inputs
18 
19Ask the user for these if not provided:
20- **Your product or company** (what you're comparing against)
21- **Competitors to analyze** (or ask to identify the top 3-5)
22- **Analysis focus** (full landscape / feature comparison / pricing / positioning / win-loss)
23- **Audience** (product team / leadership / sales / board)
24 
25## Process
26 
271. Gather competitor information from provided inputs and available context
282. Build profiles for each competitor
293. Create feature comparison matrix on dimensions that matter to the user's customers
304. Analyze pricing and positioning
315. Identify win/loss patterns and strategic implications
326. **Validate** — Confirm all claims reference a specific source or are flagged as assumptions. Verify feature comparisons note quality differences, not just presence/absence.
33 
34## Output Structure
35 
36### 1. Executive Summary
37- **Market Position**: Where we stand relative to competitors
38- **Key Findings**: Top 3-5 insights
39- **Strategic Implications**: What this means for the roadmap
40 
41### 2. Competitor Profiles
42 
43For each competitor:
44- **Company Overview**: Size, funding, market position
45- **Target Customer**: Who they serve
46- **Value Proposition**: Core positioning
47- **Strengths / Weaknesses**: What they do well and where they fall short
48- **Recent Activity**: Major updates, funding, announcements
49 
50### 3. Feature Comparison Matrix
51 
52| Feature | Us | Competitor A | Competitor B | Competitor C |
53|---------|-----|--------------|--------------|--------------|
54| [Feature] | ✅ Full | ⚠️ Limited | ❌ None | ✅ Full |
55 
56Legend: ✅ Full (production-ready) · ⚠️ Limited/Beta · ❌ None
57 
58Include notes on quality and implementation differences where significant.
59 
60### 4. Pricing Comparison
61 
62| Plan | Us | Competitor A | Competitor B |
63|------|-----|--------------|--------------|
64| Free/Trial | [price] | [price] | [price] |
65| Pro | [price] | [price] | [price] |
66| Enterprise | [price] | [price] | [price] |
67 
68### 5. Market Positioning Map
69 
70Position competitors on two key dimensions relevant to the market:
71- Y-Axis: [e.g., Enterprise vs. SMB]
72- X-Axis: [e.g., Simple vs. Comprehensive]
73 
74**Whitespace Opportunities**: [Underserved segments]
75 
76### 6. Win/Loss Analysis
77 
78**Why We Win:**
79- Better at: [specific capabilities]
80- Customers who value: [what matters to them]
81 
82**Why We Lose:**
83- When customers need: [specific requirements]
84- Their advantage: [what tips the decision]
85 
86### 7. Strategic Recommendations
87 
88**Immediate Actions (0-3 months):**
891. [Action] — [Rationale]
90 
91**Medium-term (3-12 months):**
921. [Action] — [Rationale]
93 
94## Anti-Patterns
95 
96- [ ] Do not present competitor feature claims as facts without citing a source or flagging them as assumptions — outdated or incorrect feature data misleads sales and product decisions
97- [ ] Do not build a competitive analysis that only covers features — pricing, messaging, go-to-market motion, and who they hire for are equally strategic signals
98- [ ] Do not treat all buyers as identical — the same product may win against Competitor A in the enterprise segment and lose in SMB; segment-specific win/loss matters
99- [ ] Do not soften weaknesses and threats in the SWOT to avoid internal discomfort — an honest SWOT is only useful if the negatives are real
100 
101## Deeper Materials
102 
103This skill ships with support files — use them when they are available:
104 
105- **`references/feature-matrix-honesty.md`** — Feature Matrices That Don't Lie. Apply it while producing the output; it carries the calibration and judgment calls the method summary above compresses.
106- **`templates/landscape-doc.md`** — a fill-in version of the deliverable with the quality gates inline. Offer it when the user wants to work the document themselves rather than have it generated.
107 
108## Scoring Rubric (0–40)
109 
110Score any output of this skill before handing it over; 32+ is ship-quality.
111 
112| Dimension | 0 | 5 | 10 |
113|---|---|---|---|
114| Source hygiene | Competitor claims stated as fact with no provenance; stale data presented as current | Major claims sourced, but assumptions unflagged and mixed in with verified facts | Every claim carries a source tag or explicit assumption flag; an assumption register tells the reader what to re-verify |
115| Depth beyond the feature checklist | A feature matrix and nothing else | Features plus pricing, but no positioning, GTM motion, or recent-moves analysis | Features, pricing, positioning map, and win/loss all present — with quality-difference notes where checkmark parity would mislead |
116| Segment-aware win/loss | One generic strengths/weaknesses list averaged across all buyers | Win/loss present but undifferentiated by segment or based on internal opinion, not customer evidence | Win/loss split by segment with customer-voiced reasons and deal counts; contradicting segments (win SMB, lose enterprise) shown side by side |
117| Actionability of recommendations | Generic advice ("monitor competitors", "improve differentiation") | Directionally useful actions but untethered from the findings or missing timeframes | Specific actions with timeframe and rationale, each traceable to a numbered finding — including explicit non-actions |
118 
119## Quality Checks
120 
121- [ ] All competitor claims cite a source or are flagged as assumptions
122- [ ] Feature comparison notes quality differences, not just feature presence
123- [ ] Strategic recommendations are specific actions, not generic advice
124- [ ] Win/loss analysis reflects customer perspective, not internal assumptions
125- [ ] Different customer segments are considered (not all buyers value the same things)
126 

Discussion

Alternatives

Also in Competitor researchSee all 277 in Product →
Competitor Comparison & Alternatives PagesTell us your product and a rival you keep losing deals to, and get back a ready-to-publish page that shows why customers should pick you.Business & ops · MITAd angle minerMine the highest-converting ad angles from customer reviews, Reddit complaints, support tickets, and competitor ads. Extracts actual pain language, competitor weaknesses, and outcome phrases that real buyers use. Outputs a ranked angle bank with proof quotes and recommended ad formats per angle.Business & ops · MITX audience insightsRead your X (Twitter) audience and niche from real data. Pull a handle's recent tweets (yours or a competitor's) with likes, replies, and views, see which formats and hooks are working, read the repliers on a tweet (X gates likers, so repliers are the signal), and scan a niche query for top tweets. Powered by Apify, no login. Triggers on "analyze my tweets", "what is working on X", "read the replies", "competitor tweets", "who is engaging". Not for writing a tweet (use x-post-writer).Marketing · MITFacebook Audience InsightsRead a Facebook Page and its audience from real data. Pull any Page's public stats (yours or a competitor's): followers, likes, categories, intro, websites. And pull the commenters on a public Page post, since Facebook hides the reactor and liker roster and shows counts only, so commenters are the signal. Powered by Apify, no login. Triggers on "analyze my Page", "competitor Page stats", "who is commenting", "read the comments", "audience insights". Not for writing Page posts (use fb-post-writer).Marketing · MIT