agentsclimarketplace

Market gap analysis

Skill organvm-iv-taxis/a-i--skills/skills/data/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.From its SKILL.md

Install
npx -y skills add organvm-iv-taxis/a-i--skills --skill market-gap-analysis

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 17 stars17 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

6.5 KB, as published. Nobody here has run it

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

## 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

SegmentSizeGrowthCompetitionFit
Enterprise$2B12%HighMedium
SMB$800M18%MediumHigh
Developer tools$500M25%LowHigh
Education$300M8%LowMedium

Competitive Landscape

Feature Matrix

| 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

## {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 TypeDescriptionSignal
Feature gapMissing capabilityFeature requests, workarounds
Segment gapUnserved customer typeForums, job boards, community
Price gapNo option at price pointCustomer complaints, DIY solutions
Integration gapMissing connectionStack compatibility issues
Quality gapPoor existing solutionsLow satisfaction, high churn
Geography gapUnserved regionLanguage/compliance gaps

Gap Discovery Methods

### 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

OpportunityImpact (1-10)Confidence (1-10)Ease (1-10)Score
Developer API9757.0
Mobile app6835.7
Enterprise SSO8978.0
Free tier7687.0

Score = (Impact + Confidence + Ease) / 3

RICE Framework

OpportunityReachImpactConfidenceEffortScore
Developer API500380%3 months400
Mobile app2000160%6 months200

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

StrategyWhenExample
Head-to-headStrong differentiatorBetter UX than market leader
Niche focusUnderserved segment"Built specifically for..."
Blue oceanCategory creationNew category definition
Platform playEcosystem potentialExtensibility as moat
Price disruptionOverpriced marketFree/open-source alternative

SWOT Analysis

| | 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 differentiation

Keep looking

Skills are one crate of 608,253. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.