agentleFS
isanthoshgandhiisanthoshgandhi/venture-capital-intelligence/skills/market-size/SKILL.md

market-size

Skill3 starsChanged 8 months agoMITView on GitHub

Run TAM/SAM/SOM market sizing with top-down and bottom-up methods, competitive landscape, and tech stack analysis. Triggered by: "/venture-capital-intelligence:market-size", "size this market", "what is the TAM for X", "market sizing analysis", "competitive landscape for X", "who are the competitors", "TAM SAM SOM for X", "market opportunity analysis", "how big is this market", "is this market big enough", "what's the addressable market", "total addressable market for X", "how large is the opportunity", "market research for X", "how saturated is this market", "market size estimate", "go-to-market sizing", "what is the serviceable market". Claude Code only. Requires Python 3.x. Uses web search for market data.

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. Distinctive:

    Ask for or extract:

    line 19
  2. Distinctive:

    Run 4 targeted web searches to gather market data:

    line 30
  3. Very specific:

    If bottom-up customer count is available: bottom_up_TAM = total_customers × ARPU

    line 88

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Venture Capital Intelligence — Market Size Agent

You are a market research analyst at a top-tier VC firm. You size markets rigorously using both top-down and bottom-up methods, map the competitive landscape, and assess market timing.

Pipeline: Claude web searches → Claude extracts data → Python computes TAM/SAM/SOM → Claude interprets → Python formats


STEP 1 — DEFINE THE MARKET

Ask for or extract:

  • Company name and what it does (one sentence)
  • Target customer (who buys it, what industry)
  • Geography (US only? Global? Specific region?)
  • Business model (B2B SaaS, marketplace, hardware, consumer, etc.)
  • Price point (if known)

STEP 2 — CLAUDE: WEB SEARCH FOR MARKET DATA

Run 4 targeted web searches to gather market data:

Search 1: "[market category] market size 2024 2025 billion" site:statista.com OR site:grandviewresearch.com OR site:mordorintelligence.com

Search 2: "[market category] TAM total addressable market" "$B" OR "billion" 2024

Search 3: "[target customer type] number of companies" OR "[target customer] market count" statistics

Search 4: "[company name] competitors" OR "[market category] startups" funding 2024

Extract from search results:

  • Market size estimates (note source and year)
  • Market growth rate (CAGR)
  • Number of potential customers (for bottom-up)
  • Key competitors (company name, funding, estimated revenue)

STEP 3 — CLAUDE: PREPARE SIZING INPUTS

Save to ${CLAUDE_PLUGIN_ROOT}/skills/market-size/output/market_inputs.json:

{
  "company": "",
  "market_category": "",
  "geography": "Global",
  "target_customer": "",
  "business_model": "B2B SaaS",
  "price_per_customer_annual": 0,
  "top_down": {
    "total_market_size_usd": 0,
    "addressable_fraction": 0.0,
    "obtainable_fraction": 0.0,
    "cagr_pct": 0.0,
    "source": ""
  },
  "bottom_up": {
    "total_potential_customers": 0,
    "addressable_customers": 0,
    "obtainable_customers": 0,
    "arpu_annual": 0
  },
  "competitors": [
    {
      "name": "",
      "funding_total_usd": 0,
      "estimated_arr_usd": 0,
      "founded_year": 0,
      "differentiation": ""
    }
  ]
}

Estimation guidance:

  • SAM is typically 10–30% of TAM (serviceable portion given your business model and geography)
  • SOM is typically 1–10% of SAM in years 1–3
  • If bottom-up customer count is available: bottom_up_TAM = total_customers × ARPU

STEP 4 — PYTHON: COMPUTE TAM/SAM/SOM

Run: python "${CLAUDE_PLUGIN_ROOT}/skills/market-size/scripts/tam_calculator.py"

Computes both methods and derives a consensus range. Flags if TAM < $1B (below venture threshold).


STEP 5 — CLAUDE: TECH STACK ANALYSIS

For each major competitor, identify their technology stack based on:

  • Job postings (engineering roles mention tech)
  • Open source repos (GitHub org)
  • Website technology fingerprints (CDN, analytics, tracking scripts)
  • Public developer profiles (LinkedIn, Twitter)

Classify each competitor's stack using the webappanalyzer taxonomy:

  • Frontend framework (React / Vue / Angular / Next.js)
  • Backend (Node.js / Python / Go / Ruby / Java)
  • Database (PostgreSQL / MySQL / MongoDB / Redis)
  • Infrastructure (AWS / GCP / Azure / Vercel)
  • Key SaaS tools (Stripe / Segment / Intercom / HubSpot)

This reveals: technical maturity, rebuild risk, hiring difficulty, and migration complexity for enterprise customers.


STEP 6 — PYTHON: FORMAT FINAL REPORT

Run: python "${CLAUDE_PLUGIN_ROOT}/skills/market-size/scripts/market_formatter.py"


VC MARKET RULE CHECK

After computing, flag:

  • ✅ TAM > $1B — venture-scale opportunity
  • ⚠️ TAM $500M–$1B — possible, tight for top-tier VC
  • ❌ TAM < $500M — likely too small for institutional VC (angels or PE territory)
  • ✅ Market growing > 15% CAGR — strong tailwind
  • ⚠️ Market growing 5–15% CAGR — moderate growth
  • ❌ Market declining or < 5% growth — headwind risk

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.