
Market Research
- 1.6k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/ecc
This is a copy of market-research by affaan-m - installs and ranking accrue to the original listing.
market-research is a Claude Code skill that generates sourced, decision-oriented market research, competitor breakdowns, and investor due diligence for developers who need evidence before committing build time or capital
About
market-research is a decision-oriented research skill from affaan-m/ecc that turns vague market questions into attributed intelligence developers can act on. The skill guides agents through TAM/SAM/SOM estimation, competitor and adjacent-product comparisons, fund and investor dossiers, and technology trend scans, emphasizing sourced claims over research theater. Developers reach for market-research when pressure-testing a thesis before building, fundraising, or entering a new category, and when they need structured summaries that support go/no-go calls rather than open-ended browsing. It activates on triggers like market sizing, competitive analysis, investor outreach prep, and industry intelligence that informs product or business decisions.
- Every important claim includes an explicit source
- Translates raw findings into clear decisions with separated fact/inference/recommendation sections
- Supports 5 core research modes including investor/fund diligence and competitive analysis
- Always surfaces contrarian evidence and downside cases
- Produces decision-ready summaries instead of generic research theater
Market Research by the numbers
- 1,614 all-time installs (skills.sh)
- +138 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/affaan-m/ecc --skill market-researchAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.6k |
|---|---|
| repo stars | ★ 238k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 5, 2026 |
| Repository | affaan-m/ecc ↗ |
How do you size a market with sourced competitor research?
Generate sourced, decision-oriented market research, competitor breakdowns, and investor due diligence before committing time or capital.
Who is it for?
Developers or technical founders who need attributed market intelligence and competitor breakdowns before writing code or pitching investors.
Skip if: Teams that already have validated product-market fit and only need implementation, analytics dashboards, or production monitoring setup.
When should I use this skill?
The user asks for market sizing, competitor comparisons, investor due diligence, fund research, or sourced industry intelligence before a build or funding decision.
What you get
Sourced market sizing estimates, competitor comparison tables, investor dossiers, and decision-oriented research summaries with attribution.
- competitor comparison matrix
- market sizing summary
- investor dossier
Files
Market Research
Produce research that supports decisions, not research theater.
When to Activate
- researching a market, category, company, investor, or technology trend
- building TAM/SAM/SOM estimates
- comparing competitors or adjacent products
- preparing investor dossiers before outreach
- pressure-testing a thesis before building, funding, or entering a market
Research Standards
1. Every important claim needs a source. 2. Prefer recent data and call out stale data. 3. Include contrarian evidence and downside cases. 4. Translate findings into a decision, not just a summary. 5. Separate fact, inference, and recommendation clearly.
Common Research Modes
Investor / Fund Diligence
Collect:
- fund size, stage, and typical check size
- relevant portfolio companies
- public thesis and recent activity
- reasons the fund is or is not a fit
- any obvious red flags or mismatches
Competitive Analysis
Collect:
- product reality, not marketing copy
- funding and investor history if public
- traction metrics if public
- distribution and pricing clues
- strengths, weaknesses, and positioning gaps
Market Sizing
Use:
- top-down estimates from reports or public datasets
- bottom-up sanity checks from realistic customer acquisition assumptions
- explicit assumptions for every leap in logic
Technology / Vendor Research
Collect:
- how it works
- trade-offs and adoption signals
- integration complexity
- lock-in, security, compliance, and operational risk
Output Format
Default structure: 1. executive summary 2. key findings 3. implications 4. risks and caveats 5. recommendation 6. sources
Quality Gate
Before delivering:
- all numbers are sourced or labeled as estimates
- old data is flagged
- the recommendation follows from the evidence
- risks and counterarguments are included
- the output makes a decision easier
interface:
display_name: "Market Research"
short_description: "Source-attributed market research"
brand_color: "#2563EB"
default_prompt: "Use $market-research to research markets with source-attributed findings."
policy:
allow_implicit_invocation: true
Related skills
How it compares
Choose market-research when you need sourced competitive and market intelligence before product decisions; use build-phase skills once the category and thesis are already validated.
FAQ
What does market-research produce?
market-research produces sourced market sizing (TAM/SAM/SOM), competitor breakdowns, investor dossiers, and decision-oriented summaries. The skill emphasizes attribution and conclusions that support build, fund, or pass decisions rather than unstructured notes.
When should developers use market-research?
Developers should use market-research when exploring a new category, comparing adjacent products, preparing investor outreach, or pressure-testing a thesis before writing code or raising capital. It fits pre-build and pre-funding research workflows.
Is Market Research safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.