market-sizing
Skill2 starsChanged 20 days agoMITView on GitHub
Size the market bottom-up with a source on every number, and rank entry wedges by problem quality × how much each builds the vision. Writes .claude/context/market.md. Use for "TAM", "market size", "market slide", "beachhead", "wedge", "where do we start".
31 other projects use a version of this.
Adopted by
Most recently taken up by
- writer/skillstheir own version, first seen Nov 1, 2026
- Insightful-Pipe/marketing-strategy-skillstheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- Big-LAORE/Biblioth-que-de-skillstheir own version, first seen Nov 1, 2026
- daviszhen/agent-skillstheir own version, first seen Oct 25, 2026
- varunk130/claude-code-skillstheir own version, first seen Oct 24, 2026
Used with
Projects with it also use prioritize-features, brainstorm-okrs 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.
skytiger6724Skillprioritize-features
Prioritize a backlog of feature ideas based on impact, effort, risk, and strategic alignment with top 5 recommendations. Use when prioritizing a feature backlog, making scope decisions, or ranking product ideas.
Also in 4 projects that use this
skytiger6724Skillbrainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Also in 4 projects that use this
miovragSkillstrategy-red-team
Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.
Also in 3 projects that use this
launchapp-devSkillinterview-script
Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.
Also in 4 projects that use this
About-IntelligenceSkillbeachhead-segment
Identify the first beachhead market segment for a product launch.
Also in 4 projects that use this
nandanosqlSkillcustomer-journey-map
Map the complete customer experience across all touchpoints using the NNGroup framework. Identifies pain points, emotions, and opportunities at every stage of the user journey.
Also in 5 projects that use this
- +5 more from skytiger6724
Other versions31 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 31
- 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
21 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 repository11 other files it gives its agents.
- build-statusSkill
- ecosystem-bdSkill
- fundraisingSkill
- hackathonSkill
- idea-sprintSkill
- incident-commsSkill
- launchSkill
- pitch-deckSkill
- pitch-reviewSkill
- positioningSkill
- pricingSkill
The file
Files
Market sizing
Rank where to enter → count the units it covers → price them → check against a named
top-down figure → write .claude/context/market.md. Output is one bottom-up number you can
defend factor by factor and a ranked list of entry wedges. Asked for both flows, run wedges
first, then size the top two or three, plus idea.md's wedge if it isn't among them: the
slide is sized on that one.
What investors and filed decks ask of a market slide: method-sources.md. Traps: traps.md. Read it before adding anything up.
Context handoff
- At start, read whichever of these exist, and only ask what they don't answer:
.claude/context/market.md: a re-size. Re-open every source before reusing its number.idea.md(format): the founder's wedge, a candidate in the ranking.positioning.md(format): the buyer and the alternatives.pricing.md(format): the price and the floor cost.build.md(format): What works today sets each wedge's distance D; Traction is customer evidence (Kamps: a valid alternative to a formula).
- The price ceiling is what the alternative costs the buyer. No context file stores it: work it out with pricing's cost of the bad alternative, or ask.
- On completion, write
.claude/context/market.md(format) for pitch-deck's market slide and fundraising's diligence answers. The slide is sized onidea.md's wedge, the one the deck pitches; if the top-ranked wedge differs, say so under Open decisions and leaveidea.mdtoidea-sprint.
Rules for both flows
- Units before dollars. Count accounts and units from a dated source, then price them.
- Only what was opened counts. A snippet-only number is
secondary: never summed, never on a slide. - Every number is one line in the number-with-source
format:
[inferred]for a reading,(est.)for a calculation written out on the same line. - Pages for other people hold principles and the result. Process stays in the notes.
Flow A: sizing
- Name what the market is: the spend the product replaces, not an industry category.
Ceiling = what the alternative costs the buyer; floor = the marginal cost from
pricing.md. - Bottom-up first. Accounts × units per account per year × price; a monthly count is converted on its own line, never with a loose × 12. With a bps price, the unit is the volume per account per year. The beachhead is the annual revenue at 100% share of the first market (Aulet).
- Top-down only checks, inside
market.mdand never on the slide: a named firm, its latest edition, the same cut, within an order of magnitude of the bottom-up. - Three kinds of money, never added together (money-types.md): C, current spend on the check or work the product would do; S, spend on the activity it touches; R, money at risk, which goes on the problem slide. TVL, volume and market cap are Context, outside every sum.
- Bands. Beachhead US$20M to 100M a year (Aulet's 2012 draft, marked preliminary); vision above US$1B with the most persuasive evidence (YC). Outside the band, run the reverse calculation and label it calibration, never a price.
- SOM = reachable accounts × units per account per year × price, never a share of TAM. Expansion from a material improvement (Gurley) is a mechanism with no number.
- Declare what is weak: source concentration, data years, the token or FX price and its date, cuts with no number, and the billing unit.
- Propose the slide the way pitch-deck's Market row asks: one bottom-up number, the multiplication with each factor sourced, the source on each card. Why now is its own slide. The price and the number are the founder's call.
Flow B: wedges
- Vision, cycle and pillars, one line each (qxa-rubric.md).
- Filters before the search, from how the customer operates: their decision depends on what the product observes or does; the gap costs more as they grow; solving it builds the vision. One real worked case each; the founder approves them before any search.
- Five blind fronts in parallel, one by analogy, searches capped, reports kept whole: search-front-prompt.md.
- Merge and filter before listing, then one card per candidate.
- Rank by Q×A, D only breaking ties (rubric).
- One blind review of the map, by a reader with none of the context: input, not orders.
- Result page. A buyer conversation decides among the top few.
Onchain buyers
The account count is often public; read it instead of estimating it. Protocols: DefiLlama's Solana fee overview, protocols only, grouped by parent (worked count). Users: transacting wallets, deduplicated (traction checks), in humans or teams (crypto ICP). DAOs buy through proposals and grants, so their C is in past ones. Tokens convert at a dated price. Time or work saved instead of money: accelerates-x.md.
Output
.claude/context/market.md, committed.- A one-paragraph summary for the founder: the top wedge and why, the beachhead with its calculation, the proposed slide number, and the open decisions.
- On request, the wedge result page as one self-contained HTML file.
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.

