mcpField
C
competitive-analysis

competitive-analysis

github.com/mohitagw15856Marketing & growth1.5k68 installsUpdated 1w ago
Repository

About competitive-analysis

A competitive analysis skill for product and marketing teams making product decisions. It covers competitor profiles, feature and pricing comparisons, positioning, and win/loss analysis, while requiring claims to be sourced or marked as assumptions.

Key features

  1. 01Builds competitor profiles
  2. 02Compares features, pricing, and positioning
  3. 03Analyzes customer win/loss patterns
  4. 04Produces evidence-linked strategic recommendations
  5. 05Checks sourcing and assumption labels

Use cases

  1. 01Assess a product's position against competitors
  2. 02Compare features and pricing for product planning
  3. 03Analyze wins and losses by customer segment

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mohitagw15856/pm-claude-skills --skill competitive-analysis

After installing, type/competitive-analysisin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
feature-matrix-honesty.md
worked-example.md
templates/
landscape-doc.md

Details

From the project README

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

Work from what is given. If any of these is missing, still produce the complete output: fill each gap with a reasonable assumption marked (assumed, confirm) and list those assumptions at the end. Ask a question first only when the core subject itself is missing (there is nothing to write about).

  • 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
FeatureUsCompetitor ACompetitor BCompetitor 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
PlanUsCompetitor ACompetitor 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.

Dimension0510
Source hygieneCompetitor claims stated as fact with no provenance; stale data presented as currentMajor claims sourced, but assumptions unflagged and mixed in with verified factsEvery claim carries a source tag or explicit assumption flag; an assumption register tells the reader what to re-verify
Depth beyond the feature checklistA feature matrix and nothing elseFeatures plus pricing, but no positioning, GTM motion, or recent-moves analysisFeatures, pricing, positioning map, and win/loss all present — with quality-difference notes where checkmark parity would mislead
Segment-aware win/lossOne generic strengths/weaknesses list averaged across all buyersWin/loss present but undifferentiated by segment or based on internal opinion, not customer evidenceWin/loss split by segment with customer-voiced reasons and deal counts; contradicting segments (win SMB, lose enterprise) shown side by side
Actionability of recommendationsGeneric advice ("monitor competitors", "improve differentiation")Directionally useful actions but untethered from the findings or missing timeframesSpecific 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)

Example Trigger Phrases

  • "Analyze competitors."
  • "Create competitive analysis."
  • "Compare features with competitors."
  • "Build a competitive landscape."
  • "Track competitive positioning."

Comments

Markdown supported