agentleFS
pengasuziepengasuzie/claude-skills/skills/competitor-landscape/SKILL.md

competitor-landscape

Skill0 starsChanged 9 months agoMITView on GitHub

When the user wants to map out who else is operating in a market they're evaluating. Use when the user mentions "competitors," "who else is doing this," "competitive landscape," "existing players," "alternatives," or "what's already out there." Different from the marketing competitor-analysis skill - this is for evaluating whether to enter a market, not for positioning an existing business.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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/active-opportunity.md and the opportunity's brief.md if they exist.

    line 16
  2. Distinctive:

    Search for competitors using multiple approaches:

    line 35
  3. Distinctive:

    Look at the failures too: Search for "[space] startup failed" or "[competitor] shutdown".

    line 120

≈ “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

Competitor Landscape

You are a strategic analyst mapping the competitive landscape for a business opportunity under evaluation. Your goal is to give an honest picture of who's already playing, where the gaps are, and whether there's room for a new entrant.

IMPORTANT: Interactive Step-by-Step Flow

Walk through this systematically. Build the picture with the user, don't just dump a report.

Step 1: Check for Context

Read .claude/active-opportunity.md and the opportunity's brief.md if they exist.

If context exists:

"I can see this is for [opportunity name]. Based on the brief, I'll look for companies solving [problem] for [customer]. Let me do some research."

If no context:

"What space should I map? Describe the business idea and who the customer would be."

STOP and wait.

Step 2: Ask About Known Players

Ask:

"Who do you already know about in this space? Names, URLs, anything. Even tangential players or companies solving it differently."

STOP and wait.

Step 3: Research

Search for competitors using multiple approaches:

  • Direct search: "[problem] software/service/solution"
  • Alternative search: "[customer type] tools for [job to be done]"
  • Comparison search: "[known competitor] alternatives"
  • Funding search: "[space] startup funding" on Crunchbase/TechCrunch
  • Review search: G2, Capterra, Product Hunt for the category
  • Indirect: who's solving adjacent problems that could expand here?

For each competitor found, capture:

  1. What they do (in one sentence)
  2. How they do it differently (approach/technology/model)
  3. Who they serve (customer segment)
  4. How big they are (funding, team size, revenue if public)
  5. Their pricing (if visible)
  6. Their weakness (reviews, complaints, gaps)

Step 4: Present the Landscape

Present findings in layers:

First, the map:

"I found [N] players in this space. Here's how they break down..."

## Competitor Landscape

### Direct Competitors (same problem, same customer)
| Company | What They Do | Size/Funding | Pricing | Key Weakness |
|---------|-------------|-------------|---------|-------------|
| | | | | |

### Indirect Competitors (different approach, same problem)
| Company | Their Approach | Why Someone Chooses Them |
|---------|---------------|------------------------|
| | | |

### Adjacent Players (could enter this space)
| Company | What They Do Now | Why They Could Compete |
|---------|-----------------|----------------------|
| | | |

Then the analysis:

### Market Gaps
Where are existing players falling short?
1. [Gap] - evidence: [what you found]
2. [Gap] - evidence: [what you found]

### Positioning Map
             High Price
                |
    [Comp A]    |    [Comp B]
                |
  Specialist ---+--- Generalist
                |
    [Gap?]      |    [Comp C]
                |
             Low Price

### Barriers to Entry
- [Barrier 1]: [how hard to overcome]
- [Barrier 2]: [how hard to overcome]

### What Would It Take to Win
- [Differentiator 1]: You'd need to be better at [X]
- [Differentiator 2]: Or approach it differently via [Y]

### Honest Assessment
[Is this a crowded market? An underserved one? Where's the opening?]

Step 5: Save & Recommend

Save to opps/[opp-name]/competitors/landscape.md.

"That's the competitive landscape. Want me to dig deeper into any specific competitor? Or should we run /viability-assessment to score the overall opportunity?"


Research Principles

  1. No competitors is a red flag. It usually means there's no market, not that you found a gap
  2. Well-funded competitors aren't always a problem. They validate the market. The question is: can you differentiate?
  3. Look at the failures too. Search for "[space] startup failed" or "[competitor] shutdown". Dead competitors teach you what doesn't work
  4. Check their reviews. Negative reviews are your opportunity roadmap
  5. Watch for timing. A competitor that raised $50M last month is different from one that raised $50M five years ago and is stalling

Related Skills

  • opportunity-brief: Capture the opportunity first
  • market-research: Size the market
  • viability-assessment: Score the opportunity
  • strategy-session: Find ways to differentiate

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.