agentleFS
elvismuslielvismusli/business-validator/skills/competitor-analysis/SKILL.md

competitor-analysis

Skill1 starsChanged 9 months agoMITView on GitHub

Use after idea-intake to find and analyze competitors for a business idea using web search — requires run_id from idea-intake

64 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-project-setup, app-marketing-context and 10 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.
  • JwuthriSkill

    seo-project-setup

    Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.

    Also in 11 projects that use this

  • appeekySkill

    app-marketing-context

    When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.

    Also in 6 projects that use this

  • appeekySkill

    metadata-optimization

    When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.

    Also in 6 projects that use this

  • JwuthriSkill

    openseo-release-notes

    Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.

    Also in 6 projects that use this

  • akii-technologies-ltdSkill

    keyword-clustering

    Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.

    Also in 11 projects that use this

  • MicrosoftSkill

    competitive-landscape

    Use when a branch manager asks something like \"Who are we up against in each metro\"

    Also in 11 projects that use this

  • +5 more from Jwuthri
  • +1 more from appeeky

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Use WebSearch with queries like:

    line 55
  2. Very specific:

    Ensure the output directory exists: mkdir -p docs/reports/<run_id>

    line 79

“Common” is measured: kept by at least 6 in 10 of the 53 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

Competitor Analysis

Overview

Find and analyze 5-10 competitors for a business idea. Produce a structured competitive landscape section with comparison tables and positioning insights.

<HARD-GATE> You MUST have the run_id before starting. Read the business brief at `docs/business-briefs/<run_id>.md` using the exact run_id provided. Do NOT glob for files or use "most recent". If you do not have a run_id, ask the user or invoke business-validator:idea-intake first. </HARD-GATE>

Inputs

  • run_id: Provided by idea-intake or the user (format: YYYY-MM-DD-<slug>-<hhmm>)
  • Business brief: docs/business-briefs/<run_id>.md

Output

  • File: docs/reports/<run_id>/02-competitor-analysis.md

Process

digraph competitor_analysis {
    "Verify run_id exists" [shape=box];
    "Read business brief" [shape=box];
    "Search for direct competitors" [shape=box];
    "Search for indirect competitors" [shape=box];
    "Analyze each competitor" [shape=box];
    "Build comparison matrix" [shape=box];
    "Identify gaps and opportunities" [shape=box];
    "Write 02-competitor-analysis.md" [shape=box, style=filled, fillcolor="#e8f5e9"];

    "Verify run_id exists" -> "Read business brief";
    "Read business brief" -> "Search for direct competitors";
    "Read business brief" -> "Search for indirect competitors";
    "Search for direct competitors" -> "Analyze each competitor";
    "Search for indirect competitors" -> "Analyze each competitor";
    "Analyze each competitor" -> "Build comparison matrix";
    "Build comparison matrix" -> "Identify gaps and opportunities";
    "Identify gaps and opportunities" -> "Write 02-competitor-analysis.md";
}

Step 1: Read the Business Brief

Extract the business idea, target audience, business model, and any known competitors listed by the user.

Step 2: Find Competitors

Use WebSearch with queries like:

  • "[product category] competitors"
  • "[product category] alternatives"
  • "best [product type] for [target audience]"
  • "top [industry] startups [year]"
  • Known competitor names from the brief

Identify:

  • Direct competitors (same problem, same audience)
  • Indirect competitors (same problem, different approach OR different problem, same audience)

Step 3: Analyze Each Competitor

For each competitor (aim for 5-10), research:

  • Product/service offering
  • Pricing model and tiers
  • Target market
  • Key differentiators
  • Strengths and weaknesses
  • Estimated size/funding (if available)
  • Online presence (website quality, social media)

Step 4: Write Output

Ensure the output directory exists: mkdir -p docs/reports/<run_id>

Save to docs/reports/<run_id>/02-competitor-analysis.md:

## Competitive Landscape

**Run ID:** <run_id>

### Direct Competitors

| Competitor | Product | Pricing | Target Market | Strengths | Weaknesses |
|------------|---------|---------|--------------|-----------|------------|
| [Name 1] | [desc] | [model] | [who] | [list] | [list] |

### Indirect Competitors

| Competitor | Product | How They Compete | Overlap |
|------------|---------|-----------------|---------|
| [Name] | [desc] | [explanation] | [High/Med/Low] |

### Competitive Positioning Map

| Feature / Dimension | Your Idea | Comp 1 | Comp 2 | Comp 3 |
|---------------------|-----------|--------|--------|--------|
| Price Point | [?] | [$] | [$] | [$] |
| Feature Richness | [?] | [1-5] | [1-5] | [1-5] |
| Market Focus | [?] | [who] | [who] | [who] |

### Market Gaps and Opportunities
- [Gap 1: description of unmet need]
- [Gap 2: description of underserved segment]

### Key Takeaways
- [Insight 1]
- [Insight 2]
- [Insight 3]

### Sources
- [Source 1](url)

Quality Standards

  • Minimum 5 competitors analyzed
  • Each competitor MUST have verifiable source (website URL)
  • Distinguish facts from estimates
  • Focus on actionable insights, not just data collection

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.