bundles/startup/skills/market-sizer/SKILL.md
Use this skill when users need to calculate market size (TAM/SAM/SOM), assess market opportunity, validate market potential, or determine if a market is big enough to pursue. Activates for "how big is the market," "TAM," "market sizing," or market opportunity questions.
npx skillsauth add shipshitdev/library market-sizerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Market sizing specialist applying Hexa's practical market assessment methodology. Help founders determine if their target market is big enough using rigorous bottom-up AND top-down analysis.
Hexa's Core Principle: "Make sure you can approximate how big the market is—ideally by confronting bottom-up and top-down analysis."
| Term | Definition | What It Means | |------|------------|---------------| | TAM | Total Addressable Market | Everyone who could theoretically buy | | SAM | Serviceable Available Market | The segment you can actually reach | | SOM | Serviceable Obtainable Market | What you can realistically capture in 3-5 years |
Market Size = Bottom-Up Analysis + Top-Down Analysis + Timing Assessment
TAM = Total Potential Customers × Annual Revenue Per Customer
SAM = TAM × Percentage You Can Reach
SOM = SAM × Realistic Market Share (1-5% years 1-3)
Start with industry reports, narrow to your slice.
Common Sources: Gartner, Forrester, Statista, IBISWorld, CB Insights
| Your Goal | Required SOM | Required SAM | |-----------|--------------|--------------| | Lifestyle ($500K-2M/year) | $500K-2M | $10M+ | | Venture-scale ($10M+ ARR) | $10M+ | $100M+ | | Unicorn potential ($100M+) | $100M+ | $1B+ |
The 10% Rule: If you captured 10% of SAM, would that be interesting?
The two methods should be within 2-3x of each other.
| Variance | Meaning | Action | |----------|---------|--------| | < 50% | Good alignment | Proceed with confidence | | 50-200% | Reasonable | Investigate discrepancy | | > 200% | Major misalignment | One method is wrong |
| Stage | Characteristics | Implication | |-------|-----------------|-------------| | Emerging | < $100M, few players | High risk, high reward | | Growing | 20%+ growth, new entrants | Good timing | | Mature | < 10% growth, clear leaders | Need strong wedge | | Declining | Negative growth | Avoid unless transforming |
| Skill | When to Use |
|-------|-------------|
| idea-validator | Validate the idea for this market |
| startup-icp-definer | Define ideal customer in this market |
| competitive-intelligence-analyst | Deep dive on competitors |
| fundraise-advisor | Present market size to investors |
For complete bottom-up/top-down worksheets, market dynamics assessment, timing analysis framework, output format template, market size benchmarks by business type and ACV, and common mistakes to avoid, see: references/full-guide.md
development
TypeScript refactoring and modernization guidelines from a principal specialist perspective. This skill should be used when refactoring, reviewing, or modernizing TypeScript code to ensure type safety, compiler performance, and idiomatic patterns. Triggers on tasks involving TypeScript type architecture, narrowing, generics, error handling, or migration to modern TypeScript features.
tools
Resolves TypeScript and JavaScript problems across type-level programming, performance, monorepo management, migration, and modern tooling. Invoke when diagnosing "type instantiation excessively deep" errors, migrating JS to TS, configuring strict tsconfig, debugging module resolution, or choosing between Biome/ESLint/Turborepo/Nx.
tools
Turborepo monorepo build system guidance. Triggers on: `turbo.json`, task pipelines, `dependsOn`, caching, remote cache, the `turbo` CLI, `--filter`, `--affected`, CI optimization, environment variables, internal packages, monorepo structure, and package boundaries. Use when the user configures tasks or workflows, creates packages, sets up a monorepo, shares code between apps, runs changed packages, debugs cache behavior, or works in an `apps/` plus `packages/` workspace.
tools
Provides Tailwind CSS v4 performance optimization and best practices guidelines. Triggers when writing, reviewing, or refactoring Tailwind CSS v4 code; when working with Tailwind configuration, @theme directive, utility classes, responsive design, dark mode, container queries, or CSS generation optimization.