market-sizing
Skill1 starsChanged 26 days agoMITView on GitHub
Estimate market size using TAM, SAM, and SOM with top-down and bottom-up approaches. Use when sizing a market opportunity, estimating addressable market, preparing for investor pitches, or evaluating market entry.
32 other projects use a version of this.
Adopted by
Most recently taken up by
- teodstr/boardroomtheir own version, first seen Nov 16, 2026
- solanabr/startup-builder-skilltheir own version, first seen Nov 1, 2026
- writer/skillstheir own version, first seen Nov 1, 2026
- Insightful-Pipe/marketing-strategy-skillstheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillsword for word, first seen Nov 1, 2026
- Big-LAORE/Biblioth-que-de-skillsword for word, first seen Nov 1, 2026
Other versions32 projects use a version of this.
Word for word · 8
- The-Utopia-Studio/skills★ 6100% same
- Adhamxon/claude-code-skills★ 2100% same
- skytiger6724/qwen-skills★ 2100% same
- Big-LAORE/Biblioth-que-de-skills★ 1100% same
- miovrag/claude-skills★ 1100% same
- maeng777/claude-skills★ 0100% same
- stefanomartiradonna/claude-skills★ 0100% same
- vijaysuperpositionist/skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 24
- openai/plugins★ 7.8ksame name
- OneWave-AI/claude-skills★ 378same name
- explorium-ai/gtm-skills★ 346same name
- hamzafarooq/claude-code-starter★ 145same name
- AlphaMao1/AlphaMao_Skills★ 130same name
- z1993/AlphaMao_Skills★ 130same name
- Mehdibargach/claude-code-pm-skills★ 97same name
- atypica-ai/marketing-skills★ 44same name
- raphaelxiao/mck_skills★ 32same name
- writer/skills★ 9same name
14 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository76 other files it gives its agents.
- architecture-diagramSkill
- criteria-auditSkill
- disk-space-auditSkill
- frontend-slidesSkill
- gpt-researcherSkill
- banner-designSkill
- brandSkill
- designSkill
- design-systemSkill
- slidesSkill
- ui-stylingSkill
- ui-ux-pro-maxSkill
- intended-vs-implementedSkill
- cohort-analysisSkill
- brainstorm-okrsSkill
- create-prdSkill
- job-storiesSkill
- outcome-roadmapSkill
- pre-mortemSkill
- prioritization-frameworksSkill
- release-notesSkill
- retroSkill
- sprint-planSkill
- stakeholder-mapSkill
- strategy-red-teamSkill
- summarize-meetingSkill
- test-scenariosSkill
- user-storiesSkill
- wwasSkill
- beachhead-segmentSkill
- competitive-battlecardSkill
- growth-loopsSkill
- gtm-motionsSkill
- gtm-strategySkill
- ideal-customer-profileSkill
- marketing-ideasSkill
- north-star-metricSkill
- positioning-ideasSkill
- product-nameSkill
- value-prop-statementsSkill
- competitor-analysisSkill
- customer-journey-mapSkill
- market-segmentsSkill
- sentiment-analysisSkill
- user-personasSkill
- user-segmentationSkill
- analyze-feature-requestsSkill
- brainstorm-experiments-existingSkill
- brainstorm-experiments-newSkill
- brainstorm-ideas-existingSkill
- brainstorm-ideas-newSkill
- identify-assumptions-existingSkill
- identify-assumptions-newSkill
- interview-scriptSkill
- metrics-dashboardSkill
- opportunity-solution-treeSkill
- prioritize-assumptionsSkill
- prioritize-featuresSkill
- summarize-interviewSkill
- ansoff-matrixSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
5
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
- Distinctive: line 18
If the user provides market research, industry reports, financial data, or competitor information, read and analyze them directly.
- Distinctive: line 23
Top-Down Estimation: Start from total industry size and narrow to the relevant slice
- Distinctive: line 74
Always provide both top-down and bottom-up estimates to triangulate
- Distinctive: line 75
Use web search for current industry data, analyst reports, and market benchmarks
- Distinctive: line 79
Consider currency and purchasing power parity for international markets
“Common” is measured: kept by at least 6 in 10 of the 20 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.
Files
Estimate Market Size (TAM, SAM, SOM)
Purpose
Estimate the Total Addressable Market (TAM), Serviceable Addressable Market (SAM), and Serviceable Obtainable Market (SOM) for a product. Includes both top-down and bottom-up estimation approaches, growth projections, and key assumptions to validate.
Instructions
You are a strategic market analyst specializing in market sizing, opportunity assessment, and growth forecasting.
Input
Your task is to estimate the market size for $ARGUMENTS within the specified market constraints (geography, industry vertical, customer type, etc.).
If the user provides market research, industry reports, financial data, or competitor information, read and analyze them directly. Use web search to find current market data, industry reports, and growth projections.
Analysis Steps (Think Step by Step)
- Market Definition: Define the market boundaries — what problem space, which customer segments, what geography or constraints apply
- Top-Down Estimation: Start from total industry size and narrow to the relevant slice
- Bottom-Up Estimation: Build from unit economics (customers × price × frequency) to cross-validate
- SAM Scoping: Identify which portion of TAM is realistically serviceable given product capabilities, channels, and constraints
- SOM Estimation: Estimate achievable share in the next 1-3 years based on competitive position and go-to-market capacity
- Growth Projection: Forecast how TAM, SAM, and SOM may evolve over the next 2-3 years
- Assumption Mapping: Surface the key assumptions underlying each estimate
Output Structure
Market Definition
- Problem space and customer need
- Geographic and segment boundaries
- Key constraints or scoping decisions
TAM (Total Addressable Market)
- Top-down estimate with sources and reasoning
- Bottom-up estimate for cross-validation
- Reconciliation of the two approaches
- Current TAM value (annual revenue opportunity)
SAM (Serviceable Addressable Market)
- Which portion of TAM the product can realistically serve
- Constraints: geography, language, channels, product capabilities, pricing tier
- SAM as percentage of TAM with reasoning
SOM (Serviceable Obtainable Market)
- Realistic share achievable in 1-3 years
- Basis: competitive position, go-to-market capacity, current traction
- SOM as percentage of SAM with reasoning
Market Summary Table
| Metric | Current Estimate | 2-3 Year Projection |
| TAM | ||
| SAM | ||
| SOM |
Growth Drivers & Trends
- Key factors that could expand or contract the market
- Technology, regulatory, demographic, or behavioral shifts
- Emerging segments or adjacent markets
Key Assumptions & Risks
- Critical assumptions behind each estimate (numbered)
- Confidence level for each (high / medium / low)
- How to validate the most uncertain assumptions
- What would materially change the estimates
Best Practices
- Always provide both top-down and bottom-up estimates to triangulate
- Use web search for current industry data, analyst reports, and market benchmarks
- Cite sources for market data — avoid unsupported numbers
- Be explicit about assumptions; label estimates vs. data
- Distinguish between value-based (revenue) and volume-based (users/units) sizing
- Consider currency and purchasing power parity for international markets
- Flag where estimates have wide confidence intervals
- Recommend specific data sources or research to sharpen estimates
Further Reading
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
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.

