market-gap-analysis
Analyze market positioning, identify underserved segments, and map competitive gaps using systematic frameworks. Covers SWOT analysis, competitive landscape mapping, opportunity scoring, and positioning strategy. Triggers on market analysis, competitive research, or gap identification requests.
Best use case
market-gap-analysis is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Analyze market positioning, identify underserved segments, and map competitive gaps using systematic frameworks. Covers SWOT analysis, competitive landscape mapping, opportunity scoring, and positioning strategy. Triggers on market analysis, competitive research, or gap identification requests.
Teams using market-gap-analysis should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/market-gap-analysis/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How market-gap-analysis Compares
| Feature / Agent | market-gap-analysis | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Analyze market positioning, identify underserved segments, and map competitive gaps using systematic frameworks. Covers SWOT analysis, competitive landscape mapping, opportunity scoring, and positioning strategy. Triggers on market analysis, competitive research, or gap identification requests.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agent for Product Research
Browse AI agent skills for product research, competitive analysis, customer discovery, and structured product decision support.
AI Agent for SaaS Idea Validation
Use AI agent skills for SaaS idea validation, market research, customer discovery, competitor analysis, and documenting startup hypotheses.
SKILL.md Source
# Market Gap Analysis
Identify underserved markets and competitive positioning opportunities through systematic analysis.
## Analysis Framework
```
Market Scan → Competitor Map → Gap Identification → Opportunity Scoring → Strategy
│ │ │ │ │
│ │ │ │ └─ Positioning
│ │ │ └─ Prioritized gaps
│ │ └─ Unserved/underserved areas
│ └─ Feature/capability matrix
└─ Total landscape understanding
```
## Market Scanning
### TAM/SAM/SOM Analysis
```markdown
## Market Size
### Total Addressable Market (TAM)
- Market: {broad market definition}
- Size: ${amount} ({year})
- Growth: {CAGR}%
- Source: {citation}
### Serviceable Addressable Market (SAM)
- Segment: {specific segment you can reach}
- Size: ${amount}
- Criteria: {geographic, demographic, or technical constraints}
### Serviceable Obtainable Market (SOM)
- Realistic capture: ${amount} over {timeframe}
- Assumptions: {market share %, conversion rates}
```
### Market Segmentation
| Segment | Size | Growth | Competition | Fit |
|---------|------|--------|-------------|-----|
| Enterprise | $2B | 12% | High | Medium |
| SMB | $800M | 18% | Medium | High |
| Developer tools | $500M | 25% | Low | High |
| Education | $300M | 8% | Low | Medium |
## Competitive Landscape
### Feature Matrix
```markdown
| Capability | Us | Competitor A | Competitor B | Competitor C |
|------------|:--:|:-----------:|:-----------:|:-----------:|
| Core feature 1 | ● | ● | ◐ | ○ |
| Core feature 2 | ● | ○ | ● | ● |
| Feature 3 | ◐ | ● | ○ | ○ |
| Feature 4 | ○ | ○ | ○ | ○ |
| Integration X | ● | ◐ | ● | ○ |
● = Full support ◐ = Partial ○ = None
```
### Positioning Map
```
High Price
│
Enterprise │ Premium
Solutions │ Tools
│
Low ────────┼──────── High
Innovation │ Innovation
│
Legacy │ Open Source /
Tools │ Community
│
Low Price
```
### Competitor Profiles
```markdown
## {Competitor Name}
**Positioning:** {one-sentence positioning}
**Target:** {primary customer segment}
**Pricing:** {model and range}
**Strengths:** {2-3 key strengths}
**Weaknesses:** {2-3 key weaknesses}
**Recent moves:** {latest product/market changes}
**Threat level:** High / Medium / Low
```
## Gap Identification
### Gap Types
| Gap Type | Description | Signal |
|----------|-------------|--------|
| **Feature gap** | Missing capability | Feature requests, workarounds |
| **Segment gap** | Unserved customer type | Forums, job boards, community |
| **Price gap** | No option at price point | Customer complaints, DIY solutions |
| **Integration gap** | Missing connection | Stack compatibility issues |
| **Quality gap** | Poor existing solutions | Low satisfaction, high churn |
| **Geography gap** | Unserved region | Language/compliance gaps |
### Gap Discovery Methods
```markdown
### Direct Research
- Customer interviews (5-10 per segment)
- Support ticket analysis (top 20 requests)
- Feature request boards (competitor and own)
- App store reviews (1-star and 3-star)
### Indirect Research
- Job postings (what tools are companies hiring for?)
- Stack Overflow questions (what problems remain unsolved?)
- Reddit/community forums (what workarounds exist?)
- Conference talks (what problems are speakers addressing?)
```
## Opportunity Scoring
### ICE Framework
| Opportunity | Impact (1-10) | Confidence (1-10) | Ease (1-10) | Score |
|------------|:-----:|:-----:|:-----:|:-----:|
| Developer API | 9 | 7 | 5 | 7.0 |
| Mobile app | 6 | 8 | 3 | 5.7 |
| Enterprise SSO | 8 | 9 | 7 | 8.0 |
| Free tier | 7 | 6 | 8 | 7.0 |
Score = (Impact + Confidence + Ease) / 3
### RICE Framework
| Opportunity | Reach | Impact | Confidence | Effort | Score |
|------------|:-----:|:------:|:----------:|:------:|:-----:|
| Developer API | 500 | 3 | 80% | 3 months | 400 |
| Mobile app | 2000 | 1 | 60% | 6 months | 200 |
Score = (Reach × Impact × Confidence) / Effort
## Positioning Strategy
### Positioning Statement Template
```
For {target customer}
who {need/problem},
{product name} is a {category}
that {key benefit}.
Unlike {primary competitor},
we {key differentiator}.
```
### Strategic Options
| Strategy | When | Example |
|----------|------|---------|
| **Head-to-head** | Strong differentiator | Better UX than market leader |
| **Niche focus** | Underserved segment | "Built specifically for..." |
| **Blue ocean** | Category creation | New category definition |
| **Platform play** | Ecosystem potential | Extensibility as moat |
| **Price disruption** | Overpriced market | Free/open-source alternative |
## SWOT Analysis
```markdown
| | Positive | Negative |
|---|---------|----------|
| **Internal** | **Strengths** | **Weaknesses** |
| | • {strength 1} | • {weakness 1} |
| | • {strength 2} | • {weakness 2} |
| **External** | **Opportunities** | **Threats** |
| | • {opportunity 1} | • {threat 1} |
| | • {opportunity 2} | • {threat 2} |
```
## Anti-Patterns
- **Analysis paralysis** — Set a time-box; analysis that delays action costs more than imperfect analysis
- **Competitor obsession** — Focus on customer needs, not competitor features
- **Confirmation bias** — Seek disconfirming evidence, not just supporting data
- **Static analysis** — Markets change; revisit quarterly
- **Ignoring indirect competitors** — Spreadsheets, manual processes, and "do nothing" are competitors
- **Feature parity as strategy** — Matching competitors feature-for-feature is not differentiationRelated Skills
script-analysis-dramaturgical
Comprehensive dramaturgical analysis of screenplays and scripts. Use when asked to analyze, break down, map, or provide feedback on a script. Triggers on requests involving beat mapping, act structure analysis, scene-by-scene breakdown, first-reader reports, production notes, or any comprehensive script coverage. Claude assumes combined roles of aesthete, dramaturgist, narratologist, art historian, cinephile, rhetorician, producer, academic, and first-reader.
taxonomy-modeling-design
Phase 2 of the pentaphase structural-overhaul protocol. Classifies entities, standardizes attributes, establishes relationships, and designs the access framework. Use when the user invokes phase 2 of an overhaul, asks to "design the taxonomy" or "model the structure", or has completed a landscape audit and is ready to redesign. Consumes phase-1-landscape-report.md; produces phase-2-taxonomy-model.md.
systemic-ingestion-normalization
Phase 4 of the pentaphase structural-overhaul protocol. Purges redundancies, enriches and aligns legacy entities to the new schema, executes phased ingestion into the new environment, and audits integrity. Use when the user invokes phase 4 of an overhaul, asks to "migrate the data" or "ingest into the new system", or has a configured environment ready to accept legacy entities. Consumes phase-3-environment-spec.md; produces phase-4-ingestion-report.md.
system-environment-configuration
Phase 3 of the pentaphase structural-overhaul protocol. Translates the taxonomy model into objective technical criteria, evaluates candidate mechanisms or frameworks, instantiates the chosen architecture, and programs validation rules. Use when the user invokes phase 3 of an overhaul, asks to "select a system" or "configure the environment", or has a taxonomy model and is ready to choose technology. Consumes phase-2-taxonomy-model.md; produces phase-3-environment-spec.md.
pentaphase-orchestrator
Threads the full five-phase structural-overhaul protocol — landscape discovery, taxonomy design, environment configuration, systemic ingestion, governance evolution — for any substrate the user names. Use when the user requests a structural overhaul, system redesign, or end-to-end restructuring of a documentation system, asset registry, code monorepo, knowledge base, or operational workflow; or when they explicitly invoke the pentaphase methodology. Coordinates handoffs between phase-skills and seats validation gates between phases.
landscape-discovery-audit
Phase 1 of the pentaphase structural-overhaul protocol. Inventories assets, maps current flow, identifies friction, and defines value metrics for any substrate. Use when the user invokes phase 1 of an overhaul, requests a baseline audit, asks to "discover the landscape" of a system, or wants to understand current state before redesigning. Produces phase-1-landscape-report.md.
governance-evolution-protocol
Phase 5 of the pentaphase structural-overhaul protocol. Codifies operational protocols, onboards the ecosystem of participants, programs behavior monitoring, and establishes an iteration cadence so the substrate evolves rather than calcifies. Use when the user invokes phase 5 of an overhaul, asks to "establish governance" or "lock in the protocols", or has completed ingestion and is ready to declare the substrate operational. Consumes phase-4-ingestion-report.md; produces phase-5-governance-charter.md, which closes the protocol.
dimension-surfacing
Surfaces the parallel domain dimensions implicit in a dense or minimal prompt. Use when a user prompt is small on the surface but plainly implies multiple independent domains needing different expertise; when explicitly invoked by the coliseum-orchestrator skill as Phase 1; or when the user asks "what dimensions does this prompt encode" or "what axes does this break into." Produces a named dimension set where each dimension is independently executable and not a paraphrase of another.
coliseum-dispatch
Dispatches a composed set of assignment envelopes to domain-expert subagents in parallel, in a single message with multiple Agent tool calls. Enforces the no-pingpong gate via the pingpong-detector agent before any dispatch fires. Use when invoked by the coliseum-orchestrator as Phase 3; when envelopes are already composed and the next step is parallel execution; or when the user asks to "fan out" or "dispatch in parallel." Produces a dispatch log capturing what was sent, when, and where returns land.
assignment-composition
Wraps each surfaced dimension as a self-contained 9-section autonomous-work-assignment envelope — scope, context, success criteria, allowed tools, return format, handoff — all the recipient subagent needs to execute without coming back. Use when invoked by coliseum-orchestrator as Phase 2; when dimensions are named and the next step is to make each independently dispatchable; or when the user asks "compose this as an assignment." The no-pingpong gate validates each envelope before dispatch.
workspace-autopsy-governance
Conducts a full automated autopsy of the current workspace directory to map files, identifies structural issues, proposes a restructuring plan (the signal), and establishes unified governance using templates. Use this skill when a user asks to map, restructure, reorganize, or apply new governance to an existing messy repository.
workshop-presentation-design
Design engaging workshops, conference talks, and educational presentations. Covers learning objectives, activity design, slide craft, and facilitation techniques. Triggers on workshop design, presentation prep, talk structure, or training session requests.