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.

703 stars

byEronred

View on GitHub Installation ↓

Best use case

market-movers is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Teams using market-movers 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

$curl -o ~/.claude/skills/market-movers/SKILL.md --create-dirs "https://raw.githubusercontent.com/Eronred/aso-skills/main/skills/market-movers/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/market-movers/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How market-movers Compares

Feature / Agent	market-movers	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?

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

Related Skills

market-pulse

703

from Eronred/aso-skills

When the user wants a comprehensive App Store market overview, daily/weekly market briefing, or combined view of chart movements, trending keywords, featured apps, and new releases. Also use when the user mentions "market overview", "what's happening on the App Store", "market briefing", "weekly report", "market trends", or "state of the market". For chart-specific rank changes only, see market-movers. For keyword trends only, see keyword-research.

app-marketing-context

703

from Eronred/aso-skills

When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.

ua-campaign

703

from Eronred/aso-skills

When the user wants to plan or optimize paid user acquisition campaigns. Also use when the user mentions "Apple Search Ads", "user acquisition", "paid ads", "UA", "ad campaign", "install campaign", "Facebook ads for apps", "TikTok ads", or "cost per install". For organic growth, see aso-audit. For launch-specific UA, see app-launch.

subscription-lifecycle

703

from Eronred/aso-skills

When the user wants to optimize their subscription business end-to-end — from trial start through renewal, cancellation, and win-back. Use when the user mentions "subscription lifecycle", "trial conversion", "churn", "cancellation", "win-back", "lapsed subscribers", "dunning", "billing retry", "grace period", "renewal rate", "subscriber LTV", or "resubscribe". For paywall design and pricing strategy, see monetization-strategy. For subscription analytics dashboards, see app-analytics.

seasonal-aso

703

from Eronred/aso-skills

When the user wants to optimize their App Store listing for seasonal events, holidays, or trending moments — including keyword opportunities, metadata updates, screenshot theming, and timing strategy. Use when the user mentions "seasonal", "holiday", "Christmas", "New Year", "Valentine's Day", "summer", "back to school", "seasonal keywords", "trending now", "limited time", or wants to capitalize on a calendar event. For general keyword research, see keyword-research. For full metadata rewrites, see metadata-optimization.

screenshot-optimization

703

from Eronred/aso-skills

When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.

review-management

703

from Eronred/aso-skills

When the user wants to analyze, respond to, or improve their app reviews and ratings. Also use when the user mentions "reviews", "ratings", "negative reviews", "how to get more reviews", "review response", or "my rating is dropping". For broader ASO audit, see aso-audit. For retention issues causing bad reviews, see retention-optimization.

retention-optimization

703

from Eronred/aso-skills

When the user wants to reduce churn, improve user engagement, or increase lifetime value. Also use when the user mentions "retention", "churn", "users leaving", "engagement", "DAU/MAU", "user activation", or "why are users uninstalling". For onboarding-specific issues, see app-launch. For monetization, see monetization-strategy.

rating-prompt-strategy

703

from Eronred/aso-skills

When the user wants to improve their app's star rating, increase ratings volume, optimize when and how they prompt users for a review, or recover from a bad rating period. Use when the user mentions "app rating", "star rating", "review prompt", "SKStoreReviewRequest", "In-App Review API", "ask for review", "low rating", "rating drop", "get more reviews", or "recover from 1-star". For responding to reviews, see review-management. For overall ASO health, see aso-audit.

press-and-pr

703

from Eronred/aso-skills

When the user wants to get press coverage, media mentions, or editorial features for their app — including writing press releases, pitching journalists, getting on "best apps" lists, or building an app press kit. Use when the user mentions "press", "PR", "media coverage", "TechCrunch", "journalist", "press release", "app press kit", "get featured in media", "editorial coverage", "review from a blogger", or "app launch announcement". For Apple editorial featuring, see app-store-featured. For launch strategy, see app-launch.

onboarding-optimization

703

from Eronred/aso-skills

When the user wants to improve their app's onboarding experience, increase activation rate, reduce Day 1 drop-off, or optimize the first-run flow. Use when the user mentions "onboarding", "first-run", "activation", "tutorial", "day 1 retention", "new user flow", "permission prompts", "sign-up conversion", "onboarding funnel", or "users dropping off early". For overall retention strategy, see retention-optimization. For paywall placement, see monetization-strategy.

monetization-strategy

703

from Eronred/aso-skills

When the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.