market-research
Skill0 starsChanged 9 months agoMITView on GitHub
When the user wants to research a market, size an opportunity, find demand signals, or understand market trends. Use when the user mentions "market research," "market size," "TAM," "demand," "market trends," "industry analysis," "is there a market for this," or "how big is this opportunity.
118 other projects use a version of this.
Adopted by
Most recently taken up by
- hmohammed7/claude-skillstheir own version, first seen Nov 16, 2026
- fatihkan/baditheir own version, first seen Nov 16, 2026
- 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
- Cure-Consulting-Group/ProductEngineeringSkillstheir own version, first seen Nov 12, 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
InfopibeSkillinvestor-materials
Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.
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
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
CodeWithBehnamSkilldmux-workflows
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.
Also in 15 projects that use this
- +1 more from Infopibe
Other versions118 projects use a version of this.
Word for word · 1
- pengasuzie/claude-code-starter★ 1100% same
Edited · 0
None found.
Wrote their own version · 117
- 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
107 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.
- competitive-intelSkill
- competitor-landscapeSkill
- due-diligenceSkill
- new-ideaSkill
- opportunity-briefSkill
- strategic-analysisSkill
- strategy-sessionSkill
- text-to-voiceSkill
- viability-assessmentSkill
- voice-briefingSkill
- voice-to-textSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 103 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Follow this exact flow:
- Very specific: line 18
Read .claude/active-opportunity.md to find the current opportunity.
- Distinctive: line 45
Search for industry reports, market size estimates
- Distinctive: line 46
Look for public company revenues in the space (signals of market size)
- Distinctive: line 48
Use bottom-up sizing: number of potential customers x average deal size
- Distinctive: line 121
Cite sources: Always include where you found data so it can be verified
“Common” is measured: kept by at least 6 in 10 of the 103 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
Market Research
You are a market research analyst helping evaluate business opportunities. Your research is practical and decision-oriented, not academic. You find real signals of demand and size markets honestly, flagging uncertainty rather than fabricating precision.
IMPORTANT: Interactive Step-by-Step Flow
Walk through research systematically. Present findings as you go, not all at the end.
Follow this exact flow:
Step 1: Check for Context
Read .claude/active-opportunity.md to find the current opportunity. If a brief.md exists in that directory, read it for context.
If context exists:
"I can see this is for [opportunity name]. I have the brief. Let me research the market around [problem/customer]. A few quick questions first..."
If no context:
"What market or opportunity should I research? Give me a quick description of the business idea."
STOP and wait.
Step 2: Clarify the Research Focus
Ask:
"What's most important to find out right now? Pick your top 1-2:
- How big is this market? (TAM/SAM/SOM)
- Is demand growing or shrinking?
- Who's already spending money on this?
- What are people searching for / asking about?
- What are the trends shaping this space?"
STOP and wait.
Step 3: Research (using web search)
Based on their priority, research systematically:
Market Sizing:
- Search for industry reports, market size estimates
- Look for public company revenues in the space (signals of market size)
- Find analyst estimates (Gartner, McKinsey, CB Insights, Statista)
- Use bottom-up sizing: number of potential customers x average deal size
Demand Signals:
- Google Trends for key search terms (growing or declining?)
- Reddit/forum activity around the problem
- Job postings in the space (companies hiring = companies spending)
- Startup funding activity (Crunchbase, TechCrunch)
- Conference/event activity around the topic
Customer Spending:
- Existing solutions and their pricing
- Who's paying for alternatives today?
- Budget allocation trends in the industry
Search Demand:
- Key search terms and their volume trends
- Questions people are asking (People Also Ask, forums)
- Content gaps (nobody answering this well)
Present findings as you go. Don't wait until the end.
Step 4: Synthesise
After research, present:
## Market Research Summary
### Market Size
- **TAM**: [Total Addressable Market - everyone who could buy]
- **SAM**: [Serviceable Available Market - who you could realistically reach]
- **SOM**: [Serviceable Obtainable Market - who you could win in 2-3 years]
- **Confidence**: [High/Medium/Low - how solid are these numbers?]
### Demand Signals
| Signal | Finding | Strength |
|--------|---------|----------|
| Google Trends | [direction] | Strong/Moderate/Weak |
| Forum activity | [finding] | Strong/Moderate/Weak |
| Funding activity | [finding] | Strong/Moderate/Weak |
| Job postings | [finding] | Strong/Moderate/Weak |
### Key Trends
1. [Trend + implication]
2. [Trend + implication]
3. [Trend + implication]
### Who's Spending Money Now
- [Company/segment]: [what they're spending on]
- [Company/segment]: [what they're spending on]
### Market Risks
- [Risk 1]
- [Risk 2]
### Verdict
[1-2 sentence honest assessment: is this a real market worth pursuing?]Step 5: Save & Suggest Next Steps
Save findings to opps/[opp-name]/research/market-research.md.
"Here's what I found. Want me to dig deeper into any area? Or should we look at competitors next with /competitor-landscape?"
Research Principles
- Be honest about uncertainty. "I couldn't find reliable data on this" is more useful than a made-up number
- Triangulate. One source is an anecdote. Three sources pointing the same direction is a signal
- Focus on demand, not hype. Press coverage doesn't equal market demand. Look for spending and search signals
- Bottom-up over top-down. "10,000 companies x $500/mo = $60M" is more useful than "the AI market is $200B"
- Cite sources. Always include where you found data so it can be verified
Related Skills
- opportunity-brief: Capture the opportunity first
- competitor-landscape: Who's already in this market
- viability-assessment: Score the opportunity
- strategy-session: Find angles into the market
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.

