appeeky/aso-skills

asc-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.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/appeeky/aso-skills --skill asc-metrics

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

ASC Metrics

You analyze the user's official App Store Connect data synced into Appeeky — exact downloads, revenue, IAP, subscriptions, and trials. This is first-party data, not estimates.

Prerequisites

  • Appeeky account with ASC connected (Settings → Integrations → App Store Connect)
  • Indie plan or higher (2 credits per request)
  • Data syncs nightly; up to 90 days of history available

If ASC is not connected, prompt the user to connect it at appeeky.com/settings and return.

Initial Assessment

  1. Check for app-marketing-context.md — read it for app context
  2. Ask: What do you want to analyze? (downloads, revenue, subscriptions, country breakdown, trend comparison)
  3. Ask: Which time period? (default: last 30 days)
  4. Ask: Specific app or all apps?

Fetching Data

Step 1 — List available apps

bash
GET /v1/connect/metrics/apps

Match the user's app to an app_apple_id if not already known.

Step 2 — Get overview (portfolio)

bash
GET /v1/connect/metrics?from=YYYY-MM-DD&to=YYYY-MM-DD

Step 3 — Get app detail (single app)

bash
GET /v1/connect/metrics/apps/:appId?from=YYYY-MM-DD&to=YYYY-MM-DD

Response includes: daily[], countries[], totals.

See full API reference: appeeky-connect.md

Analysis Frameworks

Period-over-Period Comparison

Fetch two equal-length windows and compare:

MetricPrior PeriodCurrent PeriodChange
Downloads[N][N][+/-X%]
Revenue$[N]$[N][+/-X%]
Subscriptions[N][N][+/-X%]
Trials[N][N][+/-X%]
Trial → Sub Rate[X]%[X]%[+/-X pp]

What to look for:

  • Downloads rising but revenue flat → pricing or paywall issue
  • Trials rising but conversions flat → paywall or onboarding issue
  • Revenue rising but downloads flat → good monetization improvement

Daily Trend Analysis

From daily[], identify:

  • Spikes — Did a feature, update, or press trigger them?
  • Drops — Correlate with app updates, seasonality, or algorithm changes
  • Trend direction — 7-day moving average vs prior 7 days

Country Breakdown

Sort countries[] by downloads and revenue:

  1. Top 5 by downloads — Are you investing in ASO for these markets?
  2. Top 5 by revenue — Higher ARPD (avg revenue per download) = prioritize ASO
  3. High downloads, low revenue — Markets with weak monetization
  4. Low downloads, high revenue — Under-tapped premium markets (localize)

Revenue Quality Check

Compute from the data:

MetricFormulaBenchmark
ARPDRevenue / Downloads> $0.05 good; > $0.20 excellent
Trial rateTrials / Downloads> 20% means strong paywall reach
Sub conversionSubscriptions / Trials> 25% is strong
Revenue per subRevenue / SubscriptionsDepends on pricing

Output Format

Performance Snapshot

📊 [App Name] — [Period]

Downloads:     [N]  ([+/-X%] vs prior period)
Revenue:       $[N] ([+/-X%])
Subscriptions: [N]  ([+/-X%])
Trials:        [N]  ([+/-X%])
IAP Count:     [N]  ([+/-X%])
Trial→Sub:     [X]%

Top Markets (downloads):
  1. [Country] — [N] downloads, $[N]
  2. [Country] — [N] downloads, $[N]
  3. [Country] — [N] downloads, $[N]

Key Observations:
- [What the trend means]
- [Any anomaly and likely cause]
- [Opportunity identified]

Recommended Actions:
1. [Specific action based on data]
2. [Specific action based on data]

Trend Alert

When a significant change (>20%) is detected, flag it:

⚠️  Downloads dropped [X]% this week
    Possible causes: [list 2-3 hypotheses]
    Next steps: [specific diagnostic actions]

Common Questions

"Why did my downloads drop?"

  1. Pull daily trend — when did it start?
  2. Check if an update shipped on that date
  3. Check keyword rankings (use keyword-research skill)
  4. Check competitor activity (use competitor-analysis skill)

"Which countries should I localize for?" Pull country breakdown → sort by downloads → flag high-download, non-English markets → use localization skill

"Is my monetization improving?" Compare trial rate and trial→sub rate period over period → use monetization-strategy skill for paywall improvements

Related Skills

  • app-analytics — Full analytics stack setup and KPI framework
  • monetization-strategy — Improve subscription conversion and paywall
  • retention-optimization — Reduce churn using the metrics as input
  • localization — Expand top-performing markets seen in country data
  • ua-campaign — Validate whether paid installs show in downloads spike

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
appeeky
커뮤니티

android-aso

When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.

설치 수
5
GitHub Stars
2.2천
업데이트
10월 6일
appeeky
커뮤니티

localization

When the user wants to localize their App Store listing for international markets. Also use when the user mentions "localization", "translate my app", "international markets", "expand to new countries", "localize metadata", or "which countries should I target". For keyword research in specific markets, see keyword-research. For metadata writing, see metadata-optimization.

설치 수
4
GitHub Stars
2.2천
업데이트
10월 6일
appeeky
커뮤니티

review-management

When the user wants to analyze, respond to, or improve their app reviews and ratings. Also use when the user mentions "reviews", "ratings", "negative reviews", "how to get more reviews", "review response", or "my rating is dropping". For broader ASO audit, see aso-audit. For retention issues causing bad reviews, see retention-optimization.

설치 수
4
GitHub Stars
2.2천
업데이트
10월 6일
appeeky
커뮤니티

web-to-app-funnel

When the user wants to design or optimize the funnel that takes web visitors into installing and onboarding the app — including smart app banners, web-to-app deep links, deferred deep links, web onboarding (Stripe-paid web flow before app install), QR codes, "open in app" CTAs, and the trade-off between paying on web vs in-app. Use when the user mentions "web to app", "smart app banner", "Stripe before app", "web paywall before install", "Branch web SDK", "web funnel for app", "AppsFlyer OneLink

설치 수
4
GitHub Stars
2.2천
업데이트
10월 6일