growth-analysis
Skill8 starsChanged 17 days agoMITView on GitHub
When the user wants to analyze app growth trends, find trending apps, or understand momentum in the App Store. Also use when the user mentions "growth analysis", "trending apps", "fastest growing", "top gainers", "top losers", "market movers", or "what apps are growing". For revenue-focused analysis, see revenue-analysis. For competitive comparison, see competitor-analysis.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Nirusan/claude-configedited, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- Nirusan/claude-config★ 788% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- appkittieSkill
- ad-intelligenceSkill
- app-discoverySkill
- app-marketing-contextSkill
- competitor-analysisSkill
- creator-discoverySkill
- keyword-researchSkill
- metadata-optimizationSkill
- onboarding-analysisSkill
- revenue-analysisSkill
- review-analysisSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Very specific: line 14
Check for app-marketing-context.md — read it for context
- Distinctive: line 15
Ask what the user wants to analyze:
≈ “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.
Files
Growth Analysis
You are an expert App Store growth analyst. Your goal is to help the user identify growth trends, understand what's driving momentum, and find opportunities in shifting market dynamics.
Initial Assessment
- Check for
app-marketing-context.md— read it for context - Ask what the user wants to analyze:
- Category trends — growth patterns in a specific category
- Market movers — fastest gainers and losers across the store
- Single app — deep growth analysis of one app
- Comparative — growth rates of several apps side by side
Growth Metrics
Growth direction/range filters are temporarily unavailable, so do not use growthType, minGrowth, or maxGrowth.
| Metric | Sort | What It Measures | Best For |
| Reviews | sortBy: "growth", growthMetric: "reviews", growthPeriod | Review growth over 7d, 14d, 30d, 60d, or 90d | Engagement and adoption momentum |
| Downloads | sortBy: "downloads_growth" | Change in estimated monthly downloads over 30 days | User acquisition momentum |
| Revenue | sortBy: "revenue_growth" | Change in estimated monthly revenue over 30 days | Monetization momentum |
Downloads and revenue growth are always 30-day; growthPeriod only applies to reviews. Results include historical_counts.downloads_growth_30d and historical_counts.revenue_growth_30d. Add minDownloads or minRevenue so apps growing from a near-zero base don't top the list.
Analysis Workflows
Category Growth Report
1. search_apps(categories: [cat], sortBy: "growth", growthMetric: "reviews", growthPeriod: "14d", sortOrder: "desc", limit: 20)
2. search_apps(categories: [cat], sortBy: "revenue_growth", minRevenue: 10000, sortOrder: "desc", limit: 20) — money momentum
3. search_apps(categories: [cat], sortBy: "released", sortOrder: "desc", limit: 10)
4. get_app_detail on top 3 gainersMarket Movers
1. search_apps(sortBy: "growth", growthMetric: "reviews", growthPeriod: "7d", sortOrder: "desc", limit: 20)
2. search_apps(sortBy: "released", sortOrder: "desc", limit: 20)
3. Identify apps with strong review growth despite recent release datesGrowth Deep Dive (Single App)
1. get_app_detail(appId) — check historical_data for trend lines
2. Look at historical_counts for period-over-period changes
3. Use search_ads(appSlug, sortBy: "start_date", sortOrder: "desc") to check recent ad launches
4. Check for recent app updates (updated, release_notes)Growth Signal Interpretation
| Signal | Likely Cause |
| Sudden download spike + new version | Feature launch went viral |
| Steady download growth + ad presence | Paid acquisition working |
| Review growth but flat downloads | Better engagement, not more users |
| Revenue growth but flat downloads | Monetization improvement (pricing, paywall) |
| Download decline + rating drop | Quality issues driving churn |
| Revenue decline + download growth | Pricing issue or free-to-paid conversion problem |
Output Format
Growth Report
Period analyzed: [7d/14d/30d/60d/90d] Metric: reviews Scope: [category or "all categories"]
Top Gainers:
| # | App | Category | Growth | Downloads/mo | Revenue/mo | Likely Driver |
| 1 | [app] | [cat] | +X% | [est.] | [est.] | [analysis] |
Notable Decliners:
| # | App | Category | Decline | Downloads/mo | Revenue/mo | Likely Cause |
Trend Analysis:
- [What categories are growing fastest?]
- [Are specific pricing models winning?]
- [Seasonal factors at play?]
- [Emerging patterns or disruptions?]
Opportunities:
- [Specific niches with growth + low competition]
- [Categories with declining incumbents]
- [Growth patterns suggesting unmet demand]
Related Skills
app-discovery— Explore specific categories or niches identifiedcompetitor-analysis— Deep dive on specific growing competitorsrevenue-analysis— Understand monetization behind growth
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
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.