market-movers

eronred/aso-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/eronred/aso-skills --skill market-movers
0 commentsdiscussion
summary

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.

skill.md

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
how to use market-movers

How to use market-movers on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add market-movers
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/eronred/aso-skills --skill market-movers

The skills CLI fetches market-movers from GitHub repository eronred/aso-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/market-movers

Reload or restart Cursor to activate market-movers. Access the skill through slash commands (e.g., /market-movers) or your agent's skill management interface.

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

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

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.751 reviews
  • Dhruvi Jain· Dec 20, 2024

    We added market-movers from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Maya Martin· Dec 20, 2024

    market-movers is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Daniel Rao· Dec 16, 2024

    I recommend market-movers for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Tariq Farah· Dec 12, 2024

    Useful defaults in market-movers — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Amina Singh· Dec 12, 2024

    market-movers reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Maya Taylor· Nov 15, 2024

    Keeps context tight: market-movers is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Oshnikdeep· Nov 11, 2024

    market-movers fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Nikhil Gupta· Nov 11, 2024

    Solid pick for teams standardizing on skills: market-movers is focused, and the summary matches what you get after install.

  • Mateo Garcia· Nov 7, 2024

    Useful defaults in market-movers — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Amina Verma· Nov 3, 2024

    I recommend market-movers for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 51

1 / 6