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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmarket-moversExecute the skills CLI command in your project's root directory to begin installation:
Fetches market-movers from eronred/aso-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate market-movers. Access via /market-movers in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
696
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
696
stars
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.
app-marketing-context.md — read it for the user's app and categoryUse 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| 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 |
For each top gainer:
| App | Rank Change | Current | Previous | Category | Rating |
|---|
For each notable gainer, analyze:
For each top loser:
| App | Rank Change | Current | Previous | Category | Rating |
|---|
For each notable loser, analyze:
Apps that appeared in the top 100 for the first time:
| App | Entered At | Category | Rating | Reviews |
|---|
Analyze:
Apps that fell out of the top 100:
| App | Previous Rank | Category | Rating |
|---|
If analyzing a specific genre:
Based on the market movements:
| Priority | Action | Why | Expected Impact |
|---|---|---|---|
| 1 | |||
| 2 | |||
| 3 |
3-5 bullet points with the most important movements and what they mean.
Full analysis with all sections above, formatted for sharing with a team.
🟢 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
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 movementsMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
We added market-movers from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
market-movers is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend market-movers for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in market-movers — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
market-movers reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: market-movers is the kind of skill you can hand to a new teammate without a long onboarding doc.
market-movers fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: market-movers is focused, and the summary matches what you get after install.
Useful defaults in market-movers — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend market-movers for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 51