asc-metrics▌
eronred/aso-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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.
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
- Check for
app-marketing-context.md— read it for app context - Ask: What do you want to analyze? (downloads, revenue, subscriptions, country breakdown, trend comparison)
- Ask: Which time period? (default: last 30 days)
- Ask: Specific app or all apps?
Fetching Data
Step 1 — List available apps
GET /v1/connect/metrics/apps
Match the user's app to an app_apple_id if not already known.
Step 2 — Get overview (portfolio)
GET /v1/connect/metrics?from=YYYY-MM-DD&to=YYYY-MM-DD
Step 3 — Get app detail (single app)
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:
| Metric | Prior Period | Current Period | Change |
|---|---|---|---|
| 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:
- Top 5 by downloads — Are you investing in ASO for these markets?
- Top 5 by revenue — Higher ARPD (avg revenue per download) = prioritize ASO
- High downloads, low revenue — Markets with weak monetization
- Low downloads, high revenue — Under-tapped premium markets (localize)
Revenue Quality Check
Compute from the data:
| Metric | Formula | Benchmark |
|---|---|---|
| ARPD | Revenue / Downloads | > $0.05 good; > $0.20 excellent |
| Trial rate | Trials / Downloads | > 20% means strong paywall reach |
| Sub conversion | Subscriptions / Trials | > 25% is strong |
| Revenue per sub | Revenue / Subscriptions | Depends 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?"
- Pull daily trend — when did it start?
- Check if an update shipped on that date
- Check keyword rankings (use
keyword-researchskill) - Check competitor activity (use
competitor-analysisskill)
"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 frameworkmonetization-strategy— Improve subscription conversion and paywallretention-optimization— Reduce churn using the metrics as inputlocalization— Expand top-performing markets seen in country dataua-campaign— Validate whether paid installs show in downloads spike
How to use asc-metrics on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add asc-metrics
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches asc-metrics from GitHub repository eronred/aso-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate asc-metrics. Access the skill through slash commands (e.g., /asc-metrics) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★75 reviews- ★★★★★Pratham Ware· Dec 28, 2024
Solid pick for teams standardizing on skills: asc-metrics is focused, and the summary matches what you get after install.
- ★★★★★Alexander Jackson· Dec 28, 2024
Registry listing for asc-metrics matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Amelia Smith· Dec 16, 2024
asc-metrics reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Sofia Harris· Dec 8, 2024
I recommend asc-metrics for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Sofia Sanchez· Dec 4, 2024
We added asc-metrics from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Sofia Huang· Nov 27, 2024
Keeps context tight: asc-metrics is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Sofia Brown· Nov 23, 2024
asc-metrics reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Sofia Liu· Nov 19, 2024
asc-metrics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Amelia Anderson· Nov 7, 2024
We added asc-metrics from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Naina Haddad· Oct 26, 2024
asc-metrics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 75