market-research
Skill0 starsChanged 5 months agoMITView on GitHub
Sizes a market, finds the wedge, and pinpoints the ideal customer profile (ICP) and their sharpest pains. Trigger when the user says things like "size my market", "who's my ICP", "is this a real market", "find my beachhead", "TAM SAM SOM", or "who feels this pain the most".
116 other projects use a version of this.
Adopted by
Most recently taken up by
- aya-taleb/mimic-skillstheir own version, first seen Nov 15, 2026
- aya-taleb/entrepreneur-skillstheir own version, first seen Nov 15, 2026
- thiefdroppers/cyber-investigator-skillstheir own version, first seen Nov 15, 2026
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- Adelie-Squad/solosquadtheir own version, first seen Nov 8, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use everything-claude-code, everything-claude-code-conventions 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.
InfopibeSkilleverything-claude-code
Also in 9 projects that use this
mryeastcodeSkilleverything-claude-code-conventions
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Also in 8 projects that use this
- InfopibeSkill
investor-outreach
Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.
Also in 22 projects that use this
shawnpangSkillcompetitor-monitoring
When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions. Also use when the user mentions "track competitors", "what are competitors doing", "competitor alerts", or "market watch".
Also in 3 projects that use this
tpavanipradeepSkillnextjs-turbopack
Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.
Also in 14 projects that use this
niloykumarbarmanSkillagent-sort
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
Also in 7 projects that use this
- +1 more from Infopibe
Other versions116 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 116
- affaan-m/ECC★ 246ksame name
- xu-xiang/everything-claude-code-zh★ 1.9ksame name
- CatCatUncle/openworkbuddy★ 413same name
- shawnpang/startup-founder-skills★ 331same name
- loulanyue/awesome-claude-notes★ 272same name
- alexsmedile/hormozi-skills★ 208same name
- okikusan-public/stock_skills★ 134same name
- cohen-liel/hivemind★ 108same name
- extruct-ai/gtm-skills★ 108same name
- tpavanipradeep/everything-claude-code★ 104same name
106 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 repository9 other files it gives its agents.
- cold-outreachSkill
- competitor-analysisSkill
- fundraising-narrativeSkill
- growth-experimentsSkill
- landing-page-copySkill
- mvp-specSkill
- pricing-experimentsSkill
- pricing-strategySkill
- tam-sam-somSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 102 edited versions we read keep these.
2
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 27
Prefer a painful niche over a lukewarm mass market.
- Distinctive: line 44
Avoid: vanity TAM ("$50B market!") with no bottom-up check.
“Common” is measured: kept by at least 6 in 10 of the 102 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
When to use
At idea or early-validation stage, when a founder needs to know whether a market is real, big enough, and reachable — and exactly which sliver to attack first.
Inputs to gather
- One-sentence description of the product/idea.
- The job-to-be-done it replaces (spreadsheet, agency, status quo).
- Any candidate customer types the founder already has in mind.
- Geography and B2B vs. B2C focus.
Process
- Frame the market top-down AND bottom-up. Top-down: TAM → SAM → SOM. Bottom-up: (# reachable customers) × (realistic annual price). If the two disagree by >10x, the idea is mis-framed — flag it.
- Define 2-3 candidate ICPs as specific roles at specific company sizes, not demographics. Score each on: acute pain, budget, reachability, urgency.
- Find the wedge — the narrowest ICP × pain combo where you can win in 90 days. Prefer a painful niche over a lukewarm mass market.
- Extract top 3 pains in the ICP's own words; rank by frequency × severity × willingness-to-pay. Note whether each pain is a vitamin or a painkiller.
- Moat check: "If OpenAI/Anthropic shipped this tomorrow, what's left?" If the answer is "nothing", push toward proprietary data, vertical depth, or workflow lock-in before scaling.
Output
- Market sizing: TAM / SAM / SOM with the one assumption each rests on.
- ICP card: role, company size, where they hang out, budget authority.
- Top 3 pains ranked, each tagged painkiller/vitamin.
- The wedge: one ICP × one pain to win first, with the 90-day reachability path.
- Moat note: the durable advantage (or the gap to close).
Quality bar & pitfalls
- Good = a stranger could repeat your ICP back to you and find 10 of them on LinkedIn.
- B2B beats B2C for early traction: annual contracts churn 10-20% vs. 40-60% for B2C subs.
- Avoid: vanity TAM ("$50B market!") with no bottom-up check; demographic ICPs ("SMBs"); vitamins dressed as painkillers. Vertical niches with proprietary data win in 2026 — don't default to "everyone".
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.