agentleFS
patonkikhpatonkikh/APES/skills/product/competitive-analysis/skill.md

competitive-analysis

Skill3 starsChanged 4 months agoMITView on GitHub

Produce a structured competitive analysis: competitor map, feature matrix, positioning gaps, and strategic recommendations. Use when evaluating markets, planning differentiation, or preparing investor/product strategy decks.

54 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use usability-test-plan, onboarding-flow and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • launchapp-devSkill

    usability-test-plan

    Design a usability test plan with tasks, success metrics, participant criteria, and facilitation guide. Use when planning moderated or unmoderated usability testing sessions.

    Also in 3 projects that use this

  • Dragoon0xSkill

    onboarding-flow

    Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.

    Also in 3 projects that use this

  • shawnpangSkill

    lead-scoring

    When a founder needs to qualify inbound leads, define their ICP, build a lead scoring model, set MQL criteria, or route prospects through pipeline stages. Activate when the user mentions lead scoring, ICP, MQL, SQL, lead qualification, inbound leads, or pipeline design.

    Also in 3 projects that use this

  • nicepkgSkill

    user-research-synthesis

    Synthesize qualitative and quantitative user research into structured insights and opportunity areas. Use when analyzing interview notes, survey responses, support tickets, or behavioral data to identify themes, build personas, or prioritize opportunities.

    Also in 4 projects that use this

  • claude-office-skillsSkill

    email-marketing

    Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics

    Also in 3 projects that use this

  • AnthropicSkill

    user-research

    Plan, conduct, and synthesize user research. Trigger with "user research plan", "interview guide", "usability test", "survey design", "research questions", or when the user needs help with any aspect of understanding their users through research.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If scope is too broad, narrow to one segment before researching.

    line 33
  2. Distinctive:

    Run per-competitor SWOT (brief) and your product SWOT against the field.

    line 75

“Common” is measured: kept by at least 6 in 10 of the 45 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
skill.md

Competitive Analysis

Purpose

Produce a structured competitive analysis: who competes, how they compare, where gaps exist, and what differentiation strategy to pursue.

Input: Product idea or category, target customer segment, known competitors (optional), geography
Output: Competitive Analysis Report with landscape map, feature matrix, SWOT per player, and strategic recommendations
Examples: See examples.md for worked input/output.


Workflow

Step 1: Define market scope

Clarify:

  • Category — what job-to-be-done or product category
  • Segment — SMB vs enterprise, geography, vertical
  • Substitutes — manual workflows, spreadsheets, status quo
  • Time horizon — current players vs emerging (12–18 months)

If scope is too broad, narrow to one segment before researching.

Step 2: Build competitor long list

SourceMethod
User inputNamed competitors
SearchCategory + "alternative", G2/Capterra categories
SubstitutesAdjacent tools solving same job
EmergingRecent funding, Product Hunt, AI-native entrants

Target 5–12 relevant players; tier into direct, indirect, substitute.

Step 3: Profile each competitor

Per competitor capture:

DimensionData
PositioningOne-line value prop
Target customerSegment and persona
Pricing modelFree/freemium/enterprise
Strengths2–3 defensible advantages
WeaknessesGaps, complaints, tech debt signals
AI capabilityNative AI vs bolt-on (if applicable)

Mark confidence: verified (public source) vs inferred (state explicitly).

Step 4: Build feature comparison matrix

Rows = capabilities users care about (from JTBD, not vendor feature lists).
Columns = top 5–8 competitors + your product (planned).

Scoring: Strong · Partial · Missing · ? Unknown

Highlight rows where no incumbent excels — white space.

Step 5: Positioning analysis

Plot on 2 axes that matter to buyers (e.g., ease vs power, price vs depth).
Identify overcrowded quadrants and open space.

Run per-competitor SWOT (brief) and your product SWOT against the field.

Step 6: Strategic recommendations

TypeOutput
Differentiation2–3 wedges competitors cannot easily copy
Table stakesFeatures you must match to be credible
AvoidAreas dominated by incumbents with network effects
PartnershipsIntegrate vs compete decisions
RisksIncumbent response, commoditization

Tie recommendations to value-proposition-designer and feature-prioritization inputs.

Step 7: Validate

Run Validation checklist.


Decision Rules

ConditionAction
<3 identifiable competitorsExpand to substitutes and manual alternatives
User claims "no competitors"Challenge; document status quo as competitor
Data older than 12 monthsFlag stale; prefer recent pricing/feature pages
Enterprise vs SMB mixSplit matrix by segment — do not blend
AI product categoryAdd AI-native comparison row (RAG, agents, eval)

Validation

  • Market scope and segment defined
  • ≥5 competitors profiled with sources cited
  • Feature matrix uses buyer-centric capabilities (≥8 rows)
  • White-space opportunities identified
  • Positioning map with labeled axes
  • SWOT for your product vs field
  • Actionable recommendations (differentiation + table stakes)
  • Confidence labels on inferred data

Anti-patterns

  • Feature laundry list — matrix rows mirror vendor marketing pages.
  • Competitor worship — copying incumbents without wedge strategy.
  • Stale analysis — pricing from 2022 in fast-moving AI markets.
  • Ignoring status quo — "Excel + email" is often the real competitor.
  • No strategic so-what — report ends at matrix without recommendations.

Best Practices

  • Interview 3–5 target users: "what did you evaluate before buying X?"
  • Weight matrix rows by customer priority (from discovery interviews).
  • Refresh competitive snapshot quarterly for AI product categories.
  • Link output to idea-validator assumptions and prd-generator non-goals.
  • Separate global players from regional niche entrants.

Output Structure

# Competitive Analysis: [Category / Product]

## Scope
[Segment, geography, horizon]

## Landscape
| Tier | Players | Role |
|------|---------|------|

## Competitor Profiles
### [Name]
[Positioning, pricing, strengths, weaknesses, AI]

## Feature Matrix
| Capability | Us | A | B | C |
|------------|----|---|---|---|

## Positioning Map
[2-axis description + placement]

## White Space
[Opportunities]

## Strategic Recommendations
| Priority | Recommendation | Rationale |
|----------|----------------|-----------|

## Sources
[URLs, dates]

Next Skills

OutcomeRecommended Skill
Refine positioningproduct/value-proposition-designer
Plan market launchgrowth/go-to-market-planner
Validate idea assumptionsproduct/idea-validator
Prioritize response featuresproduct/feature-prioritization
Write PRD with competitive contextproduct/prd-generator
Technical differentiation (AI)ai/ai-solution-architect

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.