agentleFS
Sign inStart free
hamzafarooqhamzafarooq/claude-code-starter/.claude/skills/market-sizing/SKILL.md

market-sizing

Skill145 starsChanged 6 months agoMITView on GitHub

Estimate TAM, SAM, and SOM for any market from a product description. Use when the user asks about market size, opportunity sizing, or how big a market is.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 1

    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:

    Ask the user: "Describe your product and target customer in one sentence."

    line 6

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

Ask the user: "Describe your product and target customer in one sentence."

Then produce a market sizing using a bottom-up approach:

Market Sizing: [Product Name]

TAM — Total Addressable Market

  • Who is the broadest possible buyer of this type of solution?
  • Estimate: [number] × [price point] = $[TAM]
  • Source assumption: [how you derived the number]

SAM — Serviceable Addressable Market

  • Which segment can you realistically reach with your go-to-market?
  • Estimate: [number] × [price point] = $[SAM]
  • Constraint: [what limits your reach — geography, language, vertical]

SOM — Serviceable Obtainable Market

  • What share can you capture in 3 years given your team and resources?
  • Estimate: [number] × [price point] = $[SOM]
  • Assumption: [market share % and why]

Confidence: LOW / MEDIUM / HIGH State which assumptions are weakest and what data would sharpen them.

Be direct about uncertainty. Use ranges not false precision (e.g. "$2B–$5B" not "$3.4B").

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.

Check your setup, free