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.
What this skill does
# 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
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.