mcpField
C
competitor-analysis

competitor-analysis

github.com/assimovtMarketing & growth71213 installsUpdated 36w ago
Repository

About competitor-analysis

competitor-analysis is a strategy research skill for product teams studying alternatives considered by their target audience. It combines an audience-focused feature matrix with positioning and gap analysis, including manual workarounds and doing nothing.

Key features

  1. 01Direct, indirect, and non-consumption alternatives
  2. 02Audience-focused feature matrix
  3. 03Positioning map across two axes
  4. 04Competitor gap analysis
  5. 05Pricing and business model review

Use cases

  1. 01Mapping alternatives for a target audience
  2. 02Finding positioning opportunities
  3. 03Assessing competitor gaps and switching triggers

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/assimovt/productskills --skill competitor-analysis

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

Details

From the project README

Analyze competitors to find positioning gaps, not to copy features. The goal is to understand where alternatives fail your ICP so you can win on what matters to them.

Identify All Alternatives

List every alternative your ICP considers. Three categories:

  1. Direct competitors: Products that solve the same problem for the same audience.
  2. Indirect competitors: Products that solve the problem differently or serve an adjacent audience.
  3. Non-consumption: "Do nothing" and "manual workaround" (spreadsheets, email, hiring someone). ALWAYS include these — they're often the biggest competitor.

Feature Matrix

Build a comparison table focused on what YOUR ICP cares about, not every feature that exists.

CapabilityYour ProductCompetitor ACompetitor BManual Workaround
[ICP-relevant capability]How you do itHow they do itHow they do itHow people hack it

Rate each: Strong / Adequate / Weak / Missing. Don't use checkmarks — they hide nuance. Include pricing model in the matrix — it constrains product decisions.

Example row: | Real-time collaboration | Strong (live cursors) | Weak (polling-based) | Missing | Google Docs + Slack — Adequate | So what: Their users are duct-taping two tools; our strength is their pain point.

Positioning Map

Plot competitors on two axes that matter to your ICP. Choose axes where you can credibly win at least one.

Common axis pairs:

  • Ease of use vs Power/flexibility
  • Speed to value vs Depth of solution
  • Price vs Completeness
  • Self-serve vs White-glove

The empty quadrant is your opportunity. If no quadrant is empty, you need a different framing.

Example (project management tools, ICP = small remote teams):

                    Powerful
                       |
            Jira ------+------ Linear
                       |
  Easy ----------------+---------------- Hard
                       |
     Trello -----------+------ Asana
                       |
                    Simple

Empty quadrant: Powerful + Easy. That's the opportunity.

Strategic Gap Analysis

For each competitor, answer:

  1. Who do they serve best? (Their ICP vs yours)
  2. Where are they overserving? (Features their users don't need — signals bloat)
  3. Where are they underserving? (Complaints, missing features, workarounds their users build)
  4. What would make their users switch? (The trigger event + unmet need)

Guidelines

  • CRITICAL: ALWAYS include "do nothing" and "manual workaround" as competitors. For most startups, inertia is the primary competitor.
  • NEVER just list features. Analyze positioning, strategic choices, and gaps.
  • ALWAYS focus on your ICP's needs, not the broadest possible comparison.
  • NEVER copy competitor features without understanding why they built them and whether your ICP needs them.
  • ALWAYS note competitor pricing and business model — these constrain their product decisions.
  • NEVER present a feature matrix without strategic implications. "So what?" is the question every row should answer.

Skills from productskills.

Comments

Markdown supported