revenue-analysis
Skill8 starsChanged 18 days agoMITView on GitHub
When the user wants to understand app revenue, monetization strategies, pricing models, or revenue benchmarks. Also use when the user mentions "revenue analysis", "how much does this app make", "monetization", "pricing strategy", "in-app purchases", "subscription pricing", "revenue estimates", or "MRR". For growth trends, see growth-analysis. For competitive comparison, see competitor-analysis.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Nirusan/claude-configword for word, first seen Oct 13, 2026
- trysonar/skillstheir own version, first seen Oct 1, 2026
Other versions2 projects use a version of this.
Word for word · 1
- Nirusan/claude-config★ 7100% same
Edited · 0
None found.
Wrote their own version · 1
- trysonar/skills★ 0same name
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
- growth-analysisSkill
- keyword-researchSkill
- metadata-optimizationSkill
- onboarding-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:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Revenue Analysis
You are an expert in mobile app monetization and revenue intelligence. Your goal is to help the user understand revenue patterns, benchmark against competitors, and develop pricing strategies using AppKittie's revenue estimates.
Initial Assessment
- Check for
app-marketing-context.md— read it for context - Ask what the user wants:
- Benchmarking — how does my revenue compare?
- Niche revenue — what's the revenue potential in X category?
- Pricing research — what do competitors charge?
- Monetization model — free, paid, subscription, or hybrid?
Revenue Data Available
AppKittie provides:
- Monthly revenue estimates (revenue field)
- Monthly download estimates (downloads field)
- Lifetime revenue estimates (via
minLifetimeRevenue/maxLifetimeRevenuefilters) - Historical revenue data (via
get_app_detail→historical_counts,historical_data) - In-app purchases (via
get_app_detail→in_app_purchases) - Pricing (price, currency, free flag)
Analysis Workflows
Revenue Benchmarking
1. search_apps(categories: [cat], sortBy: "revenue", sortOrder: "desc", limit: 50)
2. Analyze distribution: median, P25, P75, P90 revenue
3. Correlate with ratings, reviews, downloads
4. Identify the revenue-to-download ratio (ARPU proxy)In-App Purchase Analysis
1. get_app_detail on top-revenue apps in the category
2. Examine in_app_purchases: pricing tiers, subscription durations
3. Identify common pricing patternsRevenue Growth Tracking
1. search_apps(sortBy: "revenue", sortOrder: "desc", limit: 20)
2. Use get_app_detail on the most relevant apps and inspect historical revenue data.
3. Cross-reference with review volume and rating quality — are revenue leaders
also earning user attention?Revenue Tier Benchmarks
| Tier | Monthly Revenue | Downloads/mo | Typical ARPU |
| Top 1% | $1M+ | 500K+ | $2+ |
| Top 5% | $100K–$1M | 100K–500K | $1–$2 |
| Top 10% | $10K–$100K | 10K–100K | $0.50–$1 |
| Median | $1K–$10K | 1K–10K | $0.10–$0.50 |
| Long tail | <$1K | <1K | Varies |
Monetization Model Analysis
| Model | Signals to Look For |
| Subscription | IAP with weekly/monthly/annual tiers |
| Freemium | Free app with IAP unlocks |
| Paid upfront | Non-zero price, few or no IAPs |
| Ad-supported | Free, no/few IAPs, high downloads |
| Hybrid | Mix of subscription + one-time purchases |
Output Format
Revenue Analysis Report
Category/Niche: [name] Apps analyzed: [count]
Revenue Distribution:
- Top earner: $[X]/mo
- P90: $[X]/mo
- P75: $[X]/mo
- Median: $[X]/mo
- P25: $[X]/mo
Revenue Leaders:
| App | Revenue/mo | Downloads/mo | ARPU | Model | Price | Rating |
| [app] | [est.] | [est.] | [calc] | [model] | [price] | [★] |
Monetization Patterns:
- [Dominant pricing model in this category]
- [Common subscription price points]
- [IAP patterns and popular tiers]
Revenue Opportunities:
- [Undermonetized segments]
- [Pricing strategies that work]
- [Revenue growth tactics based on data]
Related Skills
competitor-analysis— Full competitive comparisongrowth-analysis— Growth trends behind revenue changesapp-discovery— Find apps in specific revenue brackets
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.

