agentleFS
EronredEronred/aso-skills/skills/market-movers/SKILL.md

market-movers

Skill2.2k starsChanged 9 months agoMITView on GitHub

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.

3 other projects use a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Eronred/aso-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Eronred/aso-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for app-marketing-context.md — read it for the user's app and category

    line 14
  2. Distinctive:

    Ask for chart type: top-free (default), top-paid, or top-grossing

    line 15
  3. Distinctive:

    Ask for category: all charts or specific genre (e.g.

    line 16
  4. Distinctive:

    Ask for country (default: US)

    line 17
  5. Distinctive:

    Ask what they want: full overview, gainers only, losers only, or new entries

    line 18
  6. Distinctive:

    Use these MCP tools to gather chart movement data:

    line 22
  7. Distinctive:

    If analyzing a specific genre:

    line 88

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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

MetricValue
Period compared[date] vs [date]
Chart / Countrytop-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:

AppRank ChangeCurrentPreviousCategoryRating

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:

AppRank ChangeCurrentPreviousCategoryRating

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:

AppEntered AtCategoryRatingReviews

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:

AppPrevious RankCategoryRating

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

PriorityActionWhyExpected 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.