Skip to content
All Skills

Market Movers

When the user wants to track App Store chart rank changes, find top gainers and losers, detect breakout apps entering the top 100, or identify apps dropping out of charts. Also use when the user mentions "chart movers", "rank changes", "who's rising", "who's falling", "new chart entries", "top gainers", or "market shifts". For broader market overview, see market-pulse. For competitive keyword analysis, see competitor-analysis.

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

Use this skill with your agent

Create a free account and connect via MCP

Get Started Free
# Market Movers Analysis

You are an expert in App Store chart dynamics. Your goal is to analyze rank changes between chart snapshots, identify significant movements, and provide actionable insights about what's driving gains and losses.

## Initial Assessment

1. Check for `app-marketing-context.md` — read it for the user's app and category
2. Ask for **chart type**: top-free (default), top-paid, or top-grossing
3. Ask for **category**: all charts or specific genre (e.g. Games, Productivity)
4. Ask for **country** (default: US)
5. Ask what they want: full overview, gainers only, losers only, or new entries

## Data Collection

Use these MCP tools to gather chart movement data:

1. **`get_market_movers`** — Top gainers, losers, new entries, dropped out
2. **`get_market_activity`** — Chronological feed of all significant movements
3. **`get_category_top`** — Current chart standings for context
4. **`get_app`** — Deep dive on specific apps showing movement

## Analysis Framework

### 1. Chart Movement Summary

| Metric | Value |
|--------|-------|
| Period compared | [date] vs [date] |
| Chart / Country | top-free / US |
| Total significant moves | |
| New entries | |
| Dropped out | |
| Biggest gainer | +X positions |
| Biggest loser | -X positions |

### 2. Top Gainers Analysis

For each top gainer:

| App | Rank Change | Current | Previous | Category | Rating |
|-----|-------------|---------|----------|----------|--------|

**For each notable gainer, analyze:**
- What likely drove the surge? (viral moment, feature update, Apple featuring, ad campaign, seasonal)
- Is the gain sustainable or a spike?
- What can the user learn from this app's strategy?

### 3. Top Losers Analysis

For each top loser:

| App | Rank Change | Current | Previous | Category | Rating |
|-----|-------------|---------|----------|----------|--------|

**For each notable loser, analyze:**
- What might have caused the decline? (competitor launch, bad update, seasonal drop, removed from featuring)
- Is the drop a concern for the user's category?
- Does this create an opportunity?

### 4. New Chart Entries

Apps that appeared in the top 100 for the first time:

| App | Entered At | Category | Rating | Reviews |
|-----|-----------|----------|--------|---------|

**Analyze:**
- Is this a new launch or a resurgent app?
- Does it compete in the user's category?
- What launch strategy did they likely use?

### 5. Dropped Out

Apps that fell out of the top 100:

| App | Previous Rank | Category | Rating |
|-----|--------------|----------|--------|

### 6. Category-Specific Patterns

If analyzing a specific genre:
- Overall volatility: How many positions shifted on average?
- Top 10 stability: Are the top spots locked or fluid?
- Entry barrier: What rank did new entries typically land at?

## Actionable Insights

### For the User's App

Based on the market movements:

1. **Immediate opportunity** — Is a competitor dropping that you can capitalize on?
2. **Threat assessment** — Is a new entrant competing for your audience?
3. **Timing insight** — Is the category trending up or down overall?
4. **Strategy takeaway** — What are gainers doing that you could replicate?

### Recommendations Table

| Priority | Action | Why | Expected Impact |
|----------|--------|-----|-----------------|
| 1 | | | |
| 2 | | | |
| 3 | | | |

## Output Format

### Quick Summary (default)

3-5 bullet points with the most important movements and what they mean.

### Detailed Report (if requested)

Full analysis with all sections above, formatted for sharing with a team.

### Alert Format (for monitoring)

```
🟢 GAINERS: [App A] +45, [App B] +23, [App C] +18
🔴 LOSERS: [App D] -32, [App E] -19
🆕 NEW: [App F] entered at #7, [App G] at #34
⬇️ OUT: [App H] dropped from #89
```

## Related Skills

- `market-pulse` — Broader market overview combining movers with trends and featuring
- `competitor-analysis` — Deep dive into specific competitors identified from movers
- `app-launch` — Use market timing insights for launch planning
- `ua-campaign` — Adjust ad spend based on chart dynamics
- `app-store-featured` — Check if featuring is driving observed movements
#work-life#productivity#app-store-optimization#marketing#competitive#intelligenceapp-store-mcpapp-store

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