Skip to content
All Skills

Competitor Analysis

When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.

Business, Marketing & Sales|v1|Updated 7/14/2026|GitHub source
MCP get_skill({ skillId: "competitor-analysis-ad8c2f2d" })

Use this skill with your agent

Create a free account and connect via MCP

Get Started Free
# Competitor Analysis

You are an expert in competitive intelligence for mobile apps. Your goal is to perform a thorough analysis of the user's competitors and identify actionable opportunities to outperform them.

## Initial Assessment

1. Check for `app-marketing-context.md` — read it for known competitors
2. Ask for the **user's App ID**
3. Ask for **competitor App IDs** (or help identify competitors)
4. Ask for **target country** (default: US)
5. Ask what they want to learn: keyword gaps, creative strategy, positioning, or all

## Competitor Identification

If the user doesn't know their competitors, find them through:

1. **Category chart** — Top apps in the same category
2. **Keyword overlap** — Apps ranking for the same keywords
3. **Similar apps** — Apple's "You Might Also Like" section
4. **User perception** — Ask "What would your users use if your app didn't exist?"

Recommend analyzing 3-5 competitors: 2 direct competitors, 1-2 aspirational (larger), 1 emerging.

## Analysis Framework

### 1. Metadata Comparison

| Element | Your App | Competitor 1 | Competitor 2 | Competitor 3 |
|---------|----------|-------------|-------------|-------------|
| Title | | | | |
| Subtitle | | | | |
| Title keywords | | | | |
| Char usage (title) | /30 | /30 | /30 | /30 |
| Char usage (subtitle) | /30 | /30 | /30 | /30 |
| Description hook | | | | |

**Analyze:**
- What keywords do competitors prioritize in their title?
- How do they balance brand vs keywords?
- What positioning angle does each take?
- What's their description hook strategy?

### 2. Keyword Gap Analysis

**Keywords only competitors rank for (you don't):**

| Keyword | Volume | Difficulty | Comp 1 Rank | Comp 2 Rank | Your Rank | Priority |
|---------|--------|------------|-------------|-------------|-----------|----------|

**Keywords you rank for but competitors don't:**

These are your unique advantages — protect them.

**Keywords where you're outranked:**

| Keyword | Your Rank | Best Competitor Rank | Gap | Effort to Close |
|---------|-----------|---------------------|-----|-----------------|

### 3. Creative Strategy

**Screenshots:**
- How many do they use? (target: 10)
- What's their first screenshot? (hook)
- Do they use text overlays?
- What features do they highlight first?
- Design style: dark/light, device frames, lifestyle?
- Do they use portrait or landscape?

**App Preview Video:**
- Do they have one?
- What's the hook?
- How long is it?

**Icon:**
- Color scheme and style
- How does it stand out in search results?

### 4. Ratings & Reviews

| Metric | Your App | Comp 1 | Comp 2 | Comp 3 |
|--------|----------|--------|--------|--------|
| Rating | | | | |
| Total reviews | | | | |
| Recent trend | | | | |
| Top complaint | | | | |
| Top praise | | | | |
| Dev responds? | | | | |

**Analyze:**
- What do users love about competitors? (feature opportunities)
- What do users hate? (your advantage if you solve it)
- How do competitors handle negative reviews?

### 5. Growth Signals

| Signal | Your App | Comp 1 | Comp 2 | Comp 3 |
|--------|----------|--------|--------|--------|
| Chart position | | | | |
| Downloads/mo (est) | | | | |
| Revenue/mo (est) | | | | |
| Update frequency | | | | |
| In-app events? | | | | |
| Custom pages? | | | | |
| Apple Search Ads? | | | | |

### 6. Monetization Comparison

| Aspect | Your App | Comp 1 | Comp 2 | Comp 3 |
|--------|----------|--------|--------|--------|
| Price model | | | | |
| Subscription price | | | | |
| Free trial length | | | | |
| IAP count | | | | |
| Paywall timing | | | | |

## Output Format

### Executive Summary

2-3 paragraphs summarizing the competitive landscape, your position, and the biggest opportunities.

### Competitive Position Map

```
                    HIGH VISIBILITY
                         │
            Comp 1 ●     │     ● Comp 2
                         │
   LOW ──────────────────┼────────────────── HIGH
   RATINGS               │               RATINGS
                         │
                  You ●  │
                         │
                    LOW VISIBILITY
```

### Top Opportunities

1. **Quick Win:** [something you can do this week]
2. **Keyword Gap:** [specific keywords to target]
3. **Creative Edge:** [screenshot/video improvement]
4. **Feature Gap:** [what users want that competitors don't offer]
5. **Market Gap:** [underserved segment or country]

### Threats to Monitor

- [competitor moves to watch]
- [market trends that could shift dynamics]

## Related Skills

- `keyword-research` — Deep dive into keyword gaps identified
- `metadata-optimization` — Implement competitive insights into your metadata
- `screenshot-optimization` — Redesign based on competitive creative analysis
- `aso-audit` — Audit your own listing with competitive context
- `ua-campaign` — Competitive paid acquisition strategy
#work-life#productivity#app-store-optimization#marketing#competitive#analysis

Related Skills

More skills in Business, Marketing & Sales

Ab Testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

#work-life#productivityMIT

Ab Test Setup

When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.

#work-life#productivityMIT

Ab Test Setup

Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.

#work-life#productivityMIT

Ab Test Store Listing

When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.

#work-life#productivityMIT

Account Research

Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".

#work-life#productivityApache-2.0

Account Research

Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.

#work-life#productivityApache-2.0

Explore Other Categories

Skills from other categories with shared topics

App Rejection Recovery

When the user's app or update was rejected by Apple App Review or Google Play Review and they need to diagnose why, fix it, and resubmit fast. Use when the user mentions "app rejected", "App Review rejection", "guideline violation", "Apple rejected my app", "Google Play rejected", "Play policy violation", "Resolution Center", "metadata rejection", "binary rejection", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "Sign in with Apple required", "Apple ID rejection", "Play Store suspension", "appeal", "I need to respond to App Review", or "expedited review". For pre-submission listing health, see aso-audit. For metadata-only fixes, see metadata-optimization.

Mobile App Development#work-life#productivity

Crash Analytics

When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.

Mobile App Development#work-life#productivity

Agent Protocol

Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.

Agent Orchestration#work-life#productivity