app-analytics
/app-analytics
Use when the user wants to interpret ASO.dev Measurements or App Store Connect metrics: downloads, impressions, product page views, conversion, revenue, retention, sessions, active devices, ratings, reviews, release markers, experiment impact, or before/after ASO performance.
- Author
- asodevapp ↗
- Repository
- skills ↗
- Licence
- MIT
- Last repository change
- 11.05.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.05.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when the user wants to interpret ASO.dev Measurements or App Store Connect metrics: downloads, impressions, product page views, conversion, revenue, retention, sessions, active devices, ratings, reviews, release markers, experiment impact, or before/after ASO performance.
Original author description
Use when the user wants to interpret ASO.dev Measurements or App Store Connect metrics: downloads, impressions, product page views, conversion, revenue, retention, sessions, active devices, ratings, reviews, release markers, experiment impact, or before/after ASO performance.
How it works
- ASO.dev Measurements context
- Workflow
- Launch or major update readout
- Output
- Rules
SKILL.md preview
--- name: app-analytics description: "Use when the user wants to interpret ASO.dev Measurements or App Store Connect metrics: downloads, impressions, product page views, conversion, revenue, retention, sessions, active devices, ratings, reviews, release markers, experiment impact, or before/after ASO performance." metadata: version: 1.0.0 --- # App Analytics Interpret ASO and App Store performance data and turn it into decisions for metadata, creatives, pricing, reviews, releases, and experiments. ## ASO.dev Measurements context ASO.dev Measurements compares current vs previous periods and shows release-date markers on charts. Use those release markers to connect metric changes to metadata, screenshot, pricing, event, or version changes. Common metrics: - impressions, product page views, downloads, conversion - in-app purchases, subscription/revenue metrics when available - retention, sessions, active devices - ratings, reviews, review velocity - release dates and before/after periods ## Workflow 1. Identify the question: conversion drop, install growth, revenue change, retention, experiment result, review/rating movement, or release impact. 2. Capture period, country, locale, source/channel, app version, and changed surfaces. 3. Compare current period to previous period and mark releases/campaigns. 4. Separate correlation from causation. 5. Recommend the smallest next experiment or investigation. ## Launch or major update readout For a new launch or major update, inspect the first 14 days closely when data exists: - compare daily trend against release markers and previous comparable period - watch conversion, downloads, ratings/reviews, crashes/complaint themes if supplied, and revenue/subscription starts if relevant - distinguish launch novelty, featuring/ad bursts, seasonality, and metadata/creative effects - turn findings into the next metadata, screenshot, review, pricing, or CPP/PPO action ## Output ```md # App Analytics Readout App: Market: Period: Comparison period: Question: ## Metric changes | Metric | Current | Previous | Change | Interpretation | |---|---:|---:|---:|---| ## Timeline | Date | Release/campaign/change | Metrics affected | Notes | |---|---|---|---| ## Diagnosis - Likely driver: - Alternative explanations: - Data gaps: ## Next actions | Priority | Action | Skill/tool | Success metric | |---|---|---|---| ``` ## Rules - Do not invent metrics or attribution. - Do not call a change causal without enough evidence. - Segment by country, locale, traffic source, and version when possible. - For subscription-specific churn, trial, billing, or win-back analysis, use `subscription-lifecycle`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · asodevapp/skills | 100 | MIT |
| appeeky/aso-skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version 798a8a8b7be4 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100aso-router
Single entry point that routes any ASO, App Store, Google Play, app marketing, paid UA, monetization, retention, reviews, ratings, market-intel, or app-analytics question to the correct specialist skill in this library. Use FIRST whenever the user mentions an app, App Store,… - 90aso-stats
Charts and comparisons of an app's App Store numbers over any period - keyword ranks, visibility, impressions, page views, downloads, conversion, ratings and chart positions - with what moved and why. Use when the user asks "show my downloads", "rank history", "compare this… - 100asc-metrics
When the user wants to analyze their own app's actual performance data from App Store Connect — real downloads, revenue, IAP, subscriptions, trials, or country breakdowns synced via Appeeky Connect. Use when the user asks about "my downloads", "my revenue", "how is my app… - 100plan-aso
Plan-only ASO audit of App Store and Google Play listings: keywords, localized metadata, screenshots, ratings prompts. Use when "optimize our store listing", "improve app downloads", or "ASO". Submission readiness → plan-mobile-readiness. - 100aso
Optimize an app's store listing for maximum visibility and downloads — keyword strategy, title and subtitle optimization, screenshots, preview videos, rating and review management, and A/B testing on the App Store (iOS) and Google Play (Android). Use when the user says "ASO",… - 90aso
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions "ASO," "app store optimization," "app listing," "app ranking," "app downloads," or "mobile app marketing.