deep-market-research
Skill0 starsChanged 6 months agoMITView on GitHub
Map a market end-to-end and surface explicit white-space gaps plus strategic options with named tradeoffs. Goes beyond a competitor list to a decision-ready synthesis: TAM/SAM/SOM with assumptions, 10-15 competitors grouped by archetype, customer evidence, named gaps (who/what/why-not-solved/risk), 3 strategic options with cost and what-kills-each, and a Confidence section flagging weak claims. Use instead of basic competitor-analysis or market-scan when you need a decision-ready synthesis, not just a comparison. Triggers on phrases like "market research on X", "where's the white space in X", "decision-ready market analysis of X", "competitive landscape and gaps in X", "strategic options in X market", "размотать рынок X", "найти gap на рынке X".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- tatagoncalvesof/imperatriz-toolkittheir own version, first seen May 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- tatagoncalvesof/imperatriz-toolkit★ 2same name
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 repository6 other files it gives its agents.
- ai-eval-scorerSkill
- feedback-triageSkill
- prd-builderSkill
- prd-criticSkill
- product-trio-sessionSkill
- synthetic-user-interviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
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 38
If the user gives only a one-liner, ask for the strategic question driving the research before starting.
- Distinctive: line 101
Sizing without assumptions: never produce a TAM number without saying how you got there
- Distinctive: line 103
Recommendations without tradeoffs: every strategic option has a cost.
- Distinctive: line 109
If web search is genuinely unavailable, lean on training data but flag the confidence level explicitly.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Deep Market Research
Purpose
Most "market research" prompts return a Wikipedia summary plus three obvious competitors. This skill forces a multi-phase scan that ends in an explicit gap analysis, not a list.
The goal: produce a research report a PM can hand to leadership without rewriting, and a gap section that surfaces a real strategic move, not just observations.
When to use
- Entering a new market or category and need a fast structural read
- Evaluating a strategic bet, acquisition, or expansion
- Hunting white space for a new product or feature line
- Pre-PRD: validating that the problem is worth solving at the market level
When NOT to use
- You already know the market well and need a deep technical comparison (use a focused competitor teardown instead)
- The question is about a specific account, not a market (use account research)
- You need real-time pricing or current quarterly data without web access enabled
Inputs
Required:
- Market, category, or product space (e.g. "AI coding assistants for enterprise dev teams")
Optional but improves output:
- Target ICP (industry, company size, role)
- Specific strategic question driving the research
- Constraints (geography, regulation, tech)
- Time horizon (today vs 2-3 year view)
If the user gives only a one-liner, ask for the strategic question driving the research before starting. The shape of the answer depends on it.
Process
Phase 1: Frame the market
- One-paragraph market definition with explicit scope boundaries
- Rough sizing: TAM / SAM / SOM with stated assumptions (call out where numbers are estimates vs sourced)
- Segment map: 3-5 distinct buyer or use-case segments
- Value chain: who creates value, who captures it, where margin pools sit
Phase 2: Competitor mapping
- 10-15 named players grouped by positioning archetype (e.g. "incumbents", "AI-native challengers", "vertical specialists", "open-source")
- For each: one-line positioning, target segment, pricing model, signal of momentum
- Explicitly note where information is uncertain or older than 6 months
Phase 3: Customer evidence
- Common complaints and praise patterns from public sources (G2, Reddit, communities, review sites)
- 3-5 representative direct quotes if available, paraphrased if not
- Recurring jobs-to-be-done customers describe
- What customers report as "missing" or "I wish X existed"
Phase 4: Gap synthesis
The most important phase. Surface:
- Jobs poorly served: where every option fails the customer
- Segment gaps: who is underserved or ignored
- Positioning gaps: archetypes no one is claiming
- Wedge opportunities: narrow entry points with expansion paths
Each gap must include: who, what problem, why incumbents don't solve it, and the risk that they will once it's proven.
Phase 5: Strategic options
- 3 distinct strategic moves a new entrant or existing player could make
- For each: theory of why it wins, what it requires, what kills it
- Explicit tradeoffs - never recommend without naming the cost
Output
A markdown report with these sections:
# [Market] - Deep Research Report
## Market frame
## Sizing (with assumptions)
## Segments
## Competitive landscape
## Customer evidence
## Gap analysis
## Strategic options
## Confidence and gaps in researchThe final "Confidence" section is mandatory. Flag everything that's an inference, every estimate, every claim where the underlying source is weak. PMs need to know what's load-bearing.
Common failure modes to avoid
- Listing instead of synthesizing: a list of 15 competitors with descriptions is data, not analysis. Always end with implications.
- Anchoring on famous players: include 3-5 lesser-known specialists, not just the top-of-mind names
- Sizing without assumptions: never produce a TAM number without saying how you got there
- Generic gaps: "better UX" is not a gap. "Enterprise legal teams need on-prem deployment which no major player offers" is a gap.
- Recommendations without tradeoffs: every strategic option has a cost. Name it.
Tools strategy
When web search is available, you MUST use it for Phase 2 (competitor mapping) and Phase 3 (customer evidence). Skipping web search when available is the most common failure mode of this skill and produces stale outputs that won't survive scrutiny at an offsite. The skill is fundamentally about current market state, not historical knowledge.
If web search is genuinely unavailable, lean on training data but flag the confidence level explicitly. Do not pretend to have current data you don't have.
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.

