market-sizing-builder
Skill69 starsChanged 25 days agoNo licenceView on GitHub
Build a triangulated market size for a new channel, product category, or end market — a top-down estimate from industry association, trade, and government data, and an independent bottom-up estimate built from units: for consumer channels, doors times velocity times price; for services, establishments times spend per establishment or per customer. The two are reconciled line by line, every assumption is sourced and dated or marked as an assumption, the inputs the answer moves most with are run through a sensitivity table, and the result is split explicitly into total, serviceable, and obtainable market with a range rather than a point. For private equity deal and portfolio teams sizing a portfolio company's expansion into a new channel or category, for screening the "is this a large, fragmented end market?" question before a thesis is written, and for growth-equity and long-only analysts who need a defensible number behind a TAM claim. Trigger on phrases like "how big is this market," "size the TAM," "build a bottom-up market size," "what's the SAM for this channel," "is this a large fragmented market," "how many doors and what velocity," "how much do these establishments spend on this," "sanity-check management's TAM," or "reconcile the top-down and bottom-up." Do NOT use to list the players, segments, and whitespace in a sector — use the market-map-builder skill. Do NOT use for a first-pass read of a CIM against the fund's criteria — use the cim-first-pass skill. Do NOT use for cohort, retention, and CAC/LTV analysis of a company's own customers, which works from company data rather than the market. Do NOT use for bull/base/bear valuation scenarios on a model; the sensitivity table here covers market inputs only. A market size is always a range with its construction shown, never a single headline number.
In this repository55 other files it gives its agents.
- ai-workflow-auditSkill
- ambition-upgradeSkill
- call-transcript-followupSkill
- cim-first-passSkill
- claim-sentiment-extractorSkill
- coinvest-triage-memoSkill
- conference-attendee-screenSkill
- conference-prep-plannerSkill
- credit-agreement-covenant-extractorSkill
- ddq-answer-library-curatorSkill
- ddq-red-flag-scannerSkill
- ddq-response-drafterSkill
- deal-pipeline-tracker-updaterSkill
- earnings-call-extractorSkill
- executive-briefingSkill
- expert-call-question-guideSkill
- expert-call-synthesisSkill
- fomc-statement-diffSkill
- fund-doc-consistency-checkerSkill
- fund-marketing-one-pagerSkill
- fund-news-alertSkill
- hedge-fund-diligenceSkill
- hundred-day-plan-drafterSkill
- ic-memo-drafterSkill
- ic-minutes-generatorSkill
- ic-question-anticipatorSkill
- inbox-triageSkill
- intro-email-generatorSkill
- investment-folder-organizerSkill
- investment-podcast-analyzerSkill
- investment-skill-creatorSkill
- key-debates-ledgerSkill
- linkedin-post-generatorSkill
- lp-meeting-prep-briefSkill
- lp-update-generatorSkill
- manager-ai-practices-diligenceSkill
- marketing-compliance-prescreenSkill
- market-map-builderSkill
- network-referral-path-mapperSkill
- pe-nda-reviewSkill
- performance-attribution-narratorSkill
- principal-background-briefSkill
- professional-profile-briefSkill
- public-company-first-passSkill
- public-co-unit-economicsSkill
- quarterly-letter-synthesizerSkill
- regulatory-exam-binderSkill
- relationship-status-summarizerSkill
- sellside-research-triageSkill
- side-letter-term-extractorSkill
- teach-meSkill
- tear-sheet-private-coSkill
- thesis-red-teamSkill
- waterfall-carry-checkerSkill
- weekly-market-recap-writerSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
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.

