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.
- Installs
- 3.2K
- Last 24h
- +14
- Trending rank
- #7318
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/appeeky/aso-skills --skill market-movers- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads market-movers automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
- Check for
app-marketing-context.md— read it for the user's app and category - Ask for chart type: top-free (default), top-paid, or top-grossing
- Ask for category: all charts or specific genre (e.g. Games, Productivity)
- Ask for country (default: US)
- Ask what they want: full overview, gainers only, losers only, or new entries
Data Collection
Use these MCP tools to gather chart movement data:
get_market_movers— Top gainers, losers, new entries, dropped outget_market_activity— Chronological feed of all significant movementsget_category_top— Current chart standings for contextget_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:
- Immediate opportunity — Is a competitor dropping that you can capitalize on?
- Threat assessment — Is a new entrant competing for your audience?
- Timing insight — Is the category trending up or down overall?
- 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 featuringcompetitor-analysis— Deep dive into specific competitors identified from moversapp-launch— Use market timing insights for launch planningua-campaign— Adjust ad spend based on chart dynamicsapp-store-featured— Check if featuring is driving observed movements
FAQ
What does the market-movers skill do?
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.
How do I install market-movers?
Run npx skills add https://github.com/appeeky/aso-skills --skill market-movers in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/market-movers/ (personal) or .claude/skills/market-movers/ (project).
Which AI agents can use market-movers?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is market-movers safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains market-movers?
It is published by appeeky in appeeky/aso-skills. It has 3,171 recorded installs.
More from appeeky/aso-skills
aso-audit
appeeky/aso-skills
When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking. Also use when the user mentions "ASO audit", "ASO score", "why am I not ranking", "listing review", or "optimize my app store page". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
keyword-research
appeeky/aso-skills
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
monetization-strategy
appeeky/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.
metadata-optimization
appeeky/aso-skills
When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.
competitor-analysis
appeeky/aso-skills
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.
screenshot-optimization
appeeky/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.
Popular mobile skills
design-mobile-apps
designed-by-ai/skills
Design mobile app screens with Sleek, edit Sleek projects, and implement their designs in React Native or HTML.
ios-design
uizze.sh
Design and review iOS UI/UX for iPhone apps in SwiftUI, UIKit, or React Native. Use for mobile app design, screen redesigns, navigation flows, typography, forms, keyboard and safe-area layout, and accessibility checks. Apply Apple Human Interface Guidelines and consult real product references through the optional Uizze connection.
vercel-react-native-skills
vercel-labs/agent-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
animate-expo
emilkowalski/skills
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web animation use animate.
xcode-project-setup
firebase/agent-skills
Safely modifies Xcode projects (.pbxproj) to add Swift Packages and link files. Use this skill whenever an iOS project needs dependencies installed (e.g. Firebase, Alamofire).
firebase-remote-config-basics
firebase/agent-skills
Manages Firebase Remote Config templates, feature flags, loading strategies, and SDKs (Android, iOS). Use when downloading/deploying remoteconfig JSON templates, managing version history/feature flags, setting in-app defaults, fetchAndActivate(), real-time listeners, or SDK setup. Don't use for Firebase Hosting, Auth, Firestore, Data Connect, Crashlytics, or App Hosting.