agentleFS
mikezamayiasmikezamayias/agent-skills/skills/market-pulse/SKILL.md

market-pulse

Skill1 starsChanged 29 days agoBSD-3-ClauseView on GitHub

Runs a market analysis for an app or product: competitor audit, market sizing, pricing benchmarks and MAU forecasts. Also produces revenue projections, ROI estimates and go-to-market recommendations. Use for market research, competitive or landscape analysis, revenue projections or app launch strategy.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. 0 are common, 17 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 17

    Distinctive

    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. Distinctive:

    Run a structured, parallelized market analysis that produces actionable intelligence.

    line 9
  2. Distinctive:

    Search App Store/Play Store for top 20 apps in the category

    line 34
  3. Very specific:

    Use web_fetch on App Store search URLs and competitor pages

    line 36
  4. Distinctive:

    Check sites: sensortower.com/blog, appfigures.com/resources, data.ai for public reports

    line 37
  5. Distinctive:

    Check Product Hunt launches, TechCrunch/press coverage

    line 42
  6. Distinctive:

    Check Reddit/community sentiment (search subreddits relevant to the category)

    line 43
  7. Distinctive:

    Search for "[category] app market size 2025 2026"

    line 52
  8. Distinctive:

    Check Google Trends for category keywords

    line 53
  9. Distinctive:

    Check RevenueCat blog, Adapty blog for category benchmarks

    line 62
  10. Distinctive:

    After all 4 agents return, compile into the report structure:

    line 72
  11. Distinctive:

    Write the report, present key findings to user.

    line 114
  12. Distinctive:

    Rating timing: - Ask for the rating after a win in the main app, never during onboarding and not on the way to the paywall.

    line 125
  13. Distinctive:

    Always benchmark against BOTH direct competitors and adjacent apps

    line 138
  14. Distinctive:

    If no public data exists, estimate from App Store review counts (reviews ≈ 0.5-1% of downloads)

    line 139
  15. Distinctive:

    Use conservative estimates - better to exceed projections than miss them

    line 140
  16. Distinctive:

    Use Apple's App Store pricing reference tables and Google's sub-country pricing to identify optimal tiers

    line 148
  17. Distinctive:

    Check it by listing creators in the niche and the brands that sponsor them, and by pricing 5 creators per 1,000 views before choosing the …

    line 152
  18. Distinctive:

    When analyzing multiple apps at once, spawn all Phase 1 agents for all apps simultaneously (up to 16 agents).

    line 156

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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 Pulse - App Market Analysis

Run a structured, parallelized market analysis that produces actionable intelligence.

Output

A single markdown report per app at the user-specified path (default: market-pulse/{app-name}.md) containing:

  1. Executive Summary - One-paragraph verdict
  2. Market Sizing - TAM, SAM, SOM with sources and methodology
  3. Competitor Landscape - Top 10 competitors with feature matrix
  4. Pricing Benchmark - Category pricing norms, recommended strategy
  5. Projected Metrics - MAU, DAU, retention, revenue (Month 1/3/6/12)
  6. ROI Analysis - Dev cost estimate vs projected revenue, break-even timeline
  7. Channel Strategy - Launch channels ranked by expected ROI
  8. Price Localization Strategy - Top 10 markets, PPP-adjusted pricing, psychological thresholds, recommended custom price tiers per storefront
  9. Risk Matrix - Top 5 risks with mitigation strategies
  10. Recommendations - Prioritized next steps

Workflow

Phase 1: Gather Intelligence (parallel sub-agents)

Spawn 4 research agents simultaneously:

Agent 1 - App Store Intelligence:

  • Search App Store/Play Store for top 20 apps in the category
  • For each: name, rating, review count, price, IAP model, last updated, estimated downloads
  • Use web_fetch on App Store search URLs and competitor pages
  • Check sites: sensortower.com/blog, appfigures.com/resources, data.ai for public reports

Agent 2 - Competitor Deep Dive:

  • For top 10 competitors: feature list, pricing tiers, review sentiment, App Store description
  • Check Product Hunt launches, TechCrunch/press coverage
  • Check Reddit/community sentiment (search subreddits relevant to the category)
  • Note key differentiators and weaknesses
  • For a competitor you keep watching, snapshot ad counts, active ads, ads launched in the last 30 days and follower counts weekly, and diff against the last snapshot
    • New ads suggest new angles, killed ads suggest losers, and a drop in launch rate may mean harvest mode
    • Harvest mode is an inference from one example in a third-party repo created about 2026-10-18, so label it "Likely" and not as a finding

Agent 3 - Market Sizing & Trends:

  • Research category market size (reports from Statista, Grand View Research, IBISWorld - use public summaries)
  • Search for "[category] app market size 2025 2026"
  • Check Google Trends for category keywords
  • Identify growth rate and trajectory

Agent 4 - Monetization & Pricing Research:

  • Research category pricing norms (% free, freemium, paid, subscription)
  • Average subscription price in category
  • Conversion rates (free→paid) benchmarks for the category
  • ARPU benchmarks from public reports
  • Check RevenueCat blog, Adapty blog for category benchmarks
  • Price Localization Analysis:
    • Identify top 10 revenue markets for the category
    • For each market: local purchasing power (Big Mac Index or PPP ratio), psychological price thresholds (e.g. $X.99 vs round numbers), and cultural pricing norms
    • Compare auto-converted App Store prices vs locally-optimized prices for top 3 competitors
    • Note which competitors actively localize pricing (custom price tiers per storefront) vs rely on Apple/Google auto-conversion
    • Flag markets where auto-conversion creates awkward prices (e.g. ₺299.99 instead of ₺299 in Turkey)

Phase 2: Synthesize (main agent)

After all 4 agents return, compile into the report structure:

Market Sizing Formula:

TAM = Total addressable users in category × average annual spend
SAM = TAM × % reachable via target platforms (iOS/macOS/Android)
SOM = SAM × realistic capture rate (use 0.01-0.1% for Year 1 indie app)

MAU Projection Model:

Month 1:  Launch spike × retention rate
Month 3:  Organic growth + channel acquisition
Month 6:  Steady state (organic + word-of-mouth)
Month 12: Mature state with seasonal adjustments

Assumptions:
- Launch spike: 500-2000 downloads (indie with no paid marketing)
- D30 retention: 15-25% (category benchmark)
- Monthly organic growth: 5-15% (if ASO is good)
- Conversion to paid: 2-5% (category benchmark)

Revenue Projection:

Monthly Revenue = MAU × conversion_rate × ARPU
Annual Recurring = Monthly Revenue × 12 × (1 - monthly_churn)

ROI Calculation:

Development Cost = estimated hours × <hourly opportunity cost>
Break-even = Development Cost / Monthly Net Revenue
ROI (12mo) = (Total Revenue - Total Cost) / Total Cost × 100%

Phase 3: Deliver

Write the report, present key findings to user. Include:

  • Confidence levels (High/Medium/Low) on each projection
  • Data sources cited
  • Clear assumptions stated
  • Actionable recommendations with priority

Conversion Optimization Playbook

Apply these proven conversion tactics when making recommendations:

  1. Rating timing - Ask for the rating after a win in the main app, never during onboarding and not on the way to the paywall. The rule, Apple's caps and the rejection risk are in Paywall conversion flow, order step 2.
  2. Killer onboarding - Show value in under 30 seconds. Don't explain features, show outcomes. Make them feel success before asking for anything.
  3. Free trial with card required - Removes freeloaders, pre-qualifies serious users. Increases conversion ~3x vs no-card trials.
  4. Weekly pricing tier - Monthly and yearly isn't enough. Weekly lowers commitment fear and converts users who want to "test" before going long-term. Always recommend a weekly option alongside monthly/yearly.

Include a Conversion Strategy section in every report evaluating how the app can apply each of these, with specific UX recommendations.

Tips

  • For niche apps, the TAM is small - adjust SOM expectations
  • Health/fitness apps have high competition but also high willingness-to-pay
  • Finance apps have highest ARPU but strictest regulation
  • Always benchmark against BOTH direct competitors and adjacent apps
  • If no public data exists, estimate from App Store review counts (reviews ≈ 0.5-1% of downloads)
  • Use conservative estimates - better to exceed projections than miss them
  • A third-party revenue estimate is a model output and not a store figure, so quote the vendor and the date and never present it as a niche average. One vendor's terms disclaim that its data is "complete, accurate, or up-to-date" (appkittie terms, appkittie.com/terms, read 2026-10-30).
  • A second vendor says the same in its README: revenue and download figures are estimates, "useful for orders of magnitude and for comparing apps against each other", and "not accounting", and "< $5k" means below 5,000 a month and not zero (Peekly README, read 2026-11-04). Its paywall search filters by that estimate (min_revenue), so a "$100K MRR" selection in an agent prompt means "estimated above 100,000" and the post that used it showed no result.
  • A range such as "$40K to $11M" across six apps is a spread, and its top end belongs to one app. Plan on the low or middle of the range, and check the claim against the infographic's footer before repeating a headline figure.
  • Currency conversion ≠ price localization. Auto-converted prices often miss psychological thresholds and local purchasing power. Always recommend custom price tiers for top 5-10 markets. A $4.99/mo sub auto-converts to ~₺179.99 in Turkey, but ₺149.99 may convert 2-3x better.
  • Use Apple's App Store pricing reference tables and Google's sub-country pricing to identify optimal tiers
  • Niche signals, as unsourced heuristics from MobAI's niche skill: top results averaging under 3.5 stars, fewer than 5 apps targeting a keyword, high ratings with few reviews, stale update dates, and generic apps winning a specific search
  • Score each niche 1 to 5 for competition, demand and quality gap, rank by (demand × quality gap) / competition, and search keyword variations, not one keyword
  • Creator-supply signal, from one operator's unverified opinion (X, 2026-10-21): many creators and few brands buying from them lowers the price of reach. Check it by listing creators in the niche and the brands that sponsor them, and by pricing 5 creators per 1,000 views before choosing the niche.

Multi-App Mode

When analyzing multiple apps at once, spawn all Phase 1 agents for all apps simultaneously (up to 16 agents). Group results by app in Phase 2.

Present a comparison table at the end:

| Metric          | App A    | App B    | App C    |
|-----------------|----------|----------|----------|
| TAM             | $X.XB    | $X.XB    | $X.XM    |
| SOM (Y1)        | $XXK     | $XXK     | $XXK     |
| Projected MAU   | X,XXX    | X,XXX    | XXX      |
| Monthly Revenue | $X,XXX   | $X,XXX   | $XXX     |
| Break-even      | X months | X months | X months |
| Risk Level      | Med      | High     | Low      |
| Recommendation  | Launch   | Iterate  | Launch   |

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.