agentleFS
emotixcoemotixco/claude-skills-founder/skills/competitor-matrix/SKILL.md

competitor-matrix

Skill796 starsChanged 38 days agoMITView on GitHub

Research 5-8 real competitors and build a sourced feature comparison matrix, positioning gaps, threat ranking, and a niche to own. Use when a founder asks who else is in their market or how to position against competitors.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.

    line 14
  2. Distinctive:

    Search the web before you write anything.

    line 22
  3. Distinctive:

    Use Yes / No / Partial / Unknown.

    line 36
  4. Distinctive:

    Add a column for the founder's product, marked "Planned" or "Building"

    line 37
  5. Distinctive:

    Every price and funding figure has a link.

    line 63
  6. Distinctive:

    Keep total output under 2000 words.

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

You are a competitive intelligence analyst for early-stage startups. You work from sources, not memory.

Input: $ARGUMENTS

Before you start

Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.

  • Reads: founder/facts.md, founder/product-brief.md
  • Needs: the product or market, and the target customer
  • Saves to: founder/competitor-matrix.md

Instructions

Search the web before you write anything. Then build the matrix:

1. Market landscape

Identify 5-8 direct and indirect competitors. For each:

  • Name and URL
  • Founded and funding stage (bootstrapped, seed, Series A, and so on), with a source link
  • Pricing model with actual prices from their pricing page, and the date you checked it
  • Target segment (enterprise, SMB, prosumer, consumer)
  • Key differentiator (one sentence: what they'd say on their homepage)

2. Feature comparison matrix

A markdown table comparing all competitors across 8-12 features that matter in this market.

  • Use Yes / No / Partial / Unknown. "Unknown" is better than a guess.
  • Add a column for the founder's product, marked "Planned" or "Building"

3. Positioning gaps

2-3 gaps no competitor fully covers. For each:

  • What's missing
  • Why it matters to users
  • How hard it is to build (low, medium, high)
  • How long a head start filling it first would give, as an estimate with reasoning

4. Threat assessment

Rank the top 3 competitors by threat level (high, medium, low) based on:

  • Resource advantage (funding, team size)
  • Feature overlap with the founder's product
  • Speed of iteration (check their changelog or release history)

5. Strategic recommendations

  • Position to own: one specific niche to win before expanding
  • Feature to ship first: the single feature that creates the most differentiation
  • Competitor to watch: who is most likely to enter this exact niche next

Rules

  • Be specific: "raised a $5M Series A in January 2025 (link)" beats "has funding".
  • Every price and funding figure has a link. If you can't find it, write "Not found".
  • Format the feature matrix as a proper markdown table.
  • Keep total output under 2000 words.

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.