asc-metrics
by EronredThe asc-metrics skill helps you analyze official App Store Connect performance data synced into Appeeky: downloads, revenue, IAP, subscriptions, trials, and country trends. Use it for first-party reporting, period comparisons, and app sales analysis when you need real account metrics instead of estimates.
This skill scores 79/100, which means it is a solid listing candidate for directory users who want to work with real App Store Connect metrics instead of generic analytics prompts. The repository gives enough trigger guidance, workflow steps, and constraints for an agent to know when to use it and how to start, though users should still expect some adoption friction because there are no helper scripts, reference files, or install command in the skill file.
- Very clear triggerability for first-party ASC data: it explicitly covers downloads, revenue, IAP, subscriptions, trials, and country breakdowns synced via Appeeky Connect.
- Operational workflow is spelled out with prerequisite checks and step-by-step fetching guidance, reducing guesswork for agents.
- Trust signals are decent: valid frontmatter, no placeholder markers, substantial body content, and concrete repo/file references.
- No install command or companion support files are provided, so setup and execution depend heavily on the main SKILL.md instructions.
- The skill appears tied to Appeeky and requires connected ASC access plus an Indie plan or higher, which limits usefulness for users without that environment.
Overview of asc-metrics skill
What asc-metrics does
The asc-metrics skill helps you analyze your own App Store Connect performance data as synced into Appeeky: downloads, revenue, IAP, subscriptions, trials, and country-level trends. It is built for first-party reporting, so asc-metrics is the right choice when you need actual account data rather than estimates.
Who should use it
Use the asc-metrics skill if you are comparing periods, reviewing app sales trends, checking subscription performance, or answering “how is my app doing?” with source-of-truth numbers. It is especially useful for founders, growth leads, and analysts who want a repeatable asc-metrics guide for App Store Connect reporting.
What blocks adoption
The main blockers are setup and scope: Appeeky must already be connected to App Store Connect, the account needs an Indie plan or higher, and the sync is nightly with up to 90 days of history. If you need third-party estimates, this is the wrong tool; if you need deeper subscription strategy analysis, pair it with a more specialized workflow.
How to Use asc-metrics skill
Install and check access
Use the asc-metrics install flow with npx skills add Eronred/aso-skills --skill asc-metrics. Before asking for analysis, confirm that Appeeky is connected in Settings → Integrations → App Store Connect and that your plan supports requests. If ASC is not connected, the skill expects you to fix that first.
Turn a vague ask into usable input
The asc-metrics usage pattern works best when you provide four things: the metric, the app, the time window, and the comparison. Good prompts sound like this: “Use asc-metrics to analyze revenue for app X over the last 30 days vs the prior 30 days, then highlight country changes and subscription trends.” Weak prompts like “check my app” force too many assumptions.
Files to read first
Start with SKILL.md because it contains the operational flow and prerequisites. In a larger repo, you would also inspect README.md, AGENTS.md, metadata.json, and support folders, but this skill currently appears concentrated in one file. That means the fastest path is to read the skill instructions, then immediately map them to your app and question.
Practical workflow for better output
The skill’s flow is: identify the app, clarify the analysis goal, set the period, then fetch the relevant metrics. If you already know the app_apple_id, include it; if not, ask the skill to list available apps first. For asc-metrics for Data Analysis, the best results come from asking for one primary question per run, then following up with a narrower comparison instead of a broad dashboard dump.
asc-metrics skill FAQ
Is asc-metrics for estimates or official data?
It is for official data synced from App Store Connect into Appeeky. That makes asc-metrics a fit for internal reporting and operational decisions, not competitor intelligence or market sizing.
Do I need to connect anything before using it?
Yes. The skill assumes an Appeeky account, an App Store Connect integration, and a plan that allows metric requests. If those are missing, the skill is meant to stop early and send you to setup rather than guess.
Is asc-metrics better than a normal prompt?
Usually yes, if you want structured analysis with fewer follow-up questions. A generic prompt may ask for downloads or revenue, but asc-metrics adds the workflow, constraints, and data-access assumptions needed to reach the right app and time range faster.
When should I not use asc-metrics?
Do not use it when you need estimated installs for another company, deep monetization strategy beyond raw metrics, or data older than the available sync window. In those cases, choose a different skill or a broader analytics workflow.
How to Improve asc-metrics skill
Provide the decision context first
The strongest inputs tell the skill what decision you are trying to make, not just which metric you want. For example: “I need to know whether paid acquisition is improving this month” is more useful than “show downloads,” because it guides the comparison, country split, and trend framing.
Specify the app and comparison shape
asc-metrics works better when you state the exact app, date range, and benchmark. Use inputs like “all apps,” “one app,” “last 7 days vs previous 7 days,” or “month-to-date vs same period last month” so the output is not padded with irrelevant tables.
Watch for common failure modes
The most common issue is under-specifying the request, which causes generic summaries instead of useful analysis. Another issue is asking for data outside the sync window or expecting broader business context that is not in ASC; if that happens, tighten the question to metrics the skill can actually pull.
Iterate from summary to diagnosis
Start with a high-level asc-metrics usage request, then ask a second pass for the anomaly you care about: a drop in revenue, a country spike, or a subscription conversion change. This two-step approach usually produces a better asc-metrics guide experience than trying to force one prompt to answer everything at once.