appeeky/aso-skills

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.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/appeeky/aso-skills --skill market-movers

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
appeeky
コミュニティ

rating-prompt-strategy

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.

1時間の導入数
1
GitHub Stars
2316
更新日
11月13日
appeeky
コミュニティ

android-aso

When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.

1時間の導入数
1
GitHub Stars
2291
更新日
11月10日
appeeky
コミュニティ

app-icon-optimization

When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.

1時間の導入数
1
GitHub Stars
2288
更新日
11月10日
appeeky
コミュニティ

ab-test-store-listing

When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.

1時間の導入数
2
GitHub Stars
2256
更新日
10月6日