Competitor analysis

01What is it?
Analyze competitive landscape with feature matrices, positioning maps, and strategic gap analysis. Its edge is a particular angle on competitive research, giving the agent tighter constraints than a plain competitor analysis request.
02Inputs
Context for competitive research: your goals, audience, constraints, and any source material the skill asks for.
03Output
A ready-to-use result for competitive research: the analysis, copy, or recommendations the agent produces.
Paste-ready

Install as a package

Installs this one skill package for your coding agent, including any supporting files that skill ships with — not every skill in the repository. Read the tutorial.

Terminal
$ npx skills add assimovt/productskills --skill competitor-analysis

Use in Profound

Copy this file into a new Profound Skill. That's it, nothing else to install.

Copy and create in Profound
SKILL.md

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 (https://github.com/assimovt/productskills).

How do I install Competitor analysis in Cursor, Claude Code, or Codex?

Run npx skills add assimovt/productskills --skill competitor-analysis in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Competitor analysis, not every skill in the repository.

Where does Competitor analysis come from and what license is it under?

Competitor analysis comes from the assimovt/productskills repository on GitHub. That repository has 60 GitHub stars. The skill is published under the MIT license.

Prefer plain text? Read the Competitor analysis guide as markdown.