agentsclimarketplace

Sales daily report

Skill fengyiqicoder/AppMate/skills/sales-daily-report

Generate the App Store sales & downloads daily report for all live apps. Use when the user asks for a sales report, a revenue/downloads summary, daily numbers across their apps, or "跑日报".From its SKILL.md

Install
npx -y skills add fengyiqicoder/AppMate --skill sales-daily-report

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

7.3 KB, as published. Nobody here has run it

Sales & Downloads Daily Report

Run one sales & download report covering every live app, output as markdown.

Step 0 — Prerequisites (credentials must be configured)

Every step in this skill calls App Store Connect APIs. Before any other step, run:

python3 scripts/appmate_config.py check

If exit code ≠ 0, STOP. Do not invoke any other part of this skill, do not run scripts/sales_report.py. Tell the user AppMate credentials are not configured, show the precheck output verbatim, and tell them to invoke the appmate-setup skill. The downstream script also enforces this gate (exits 2 with the same message), but the explicit precheck saves you from spinning up the full 65-day fetch.

One-line summary

Pull ~65 days of daily reports from App Store Connect → aggregate across 5 time dimensions → totals + Top-3 apps + share + percentage change → markdown report.

Input / Output / Trigger

ItemContent
Triggerpython3 scripts/sales_report.py (0 args, 0 user intervention)
Inputdata/apps_full.json (live-app list) + data/sales_cache.json (historical daily reports)
Outputstdout markdown + data/report.md file + Claude pastes the full markdown back into the conversation

User intervention points

Zero. Fully automatic. The script generates the report → the file lands → Claude must paste the complete report into the conversation reply. It must not just say "saved to report.md" or post only a summary. The file is a side product; the conversation reply is the primary delivery.

The 5 time dimensions (fixed order, do not reorder)

DimensionCurrent rangeCompared to
YesterdayDATA_TODAY (most recent day with data)the day before
Last 7 daysDATA_TODAY back 7 daysthe prior 7 days
Last 30 daysDATA_TODAY back 30 daysthe prior 30 days
This weekthis Monday → DATA_TODAY(shows "Data not yet published by Apple" if this week's data is not in yet)
This monththe 1st → DATA_TODAYthe entire previous month (not the same day range)

Workflow (the script does this automatically in one pass)

  1. Load data/sales_cache.json — missing dates are fetched from ASC /v1/salesReports; gzipped TSV is decoded and cached; failed dates are recorded as _error and retried next run; empty caches for the last 3 days are auto-refreshed (Apple data can be delayed).
  2. Anchor DATA_TODAY — scan backward from today for the first date that actually has data (Apple's daily report usually lags 1-2 days).
  3. Aggregate by day — parse each TSV row (Title / Country Code / Units / Developer Proceeds × FX → USD); classify downloads by Product Type Identifier; merge IAP rows into their parent app via Parent Identifier (SKU).
  4. Slice + sum across the 5 dimensions, compute delta — per dimension: total revenue + total downloads + previous-period percentage change + Top-3 (by revenue / by downloads).
  5. Render markdown per the template below.

Report template (v1 — follow exactly)

Rendered in the same language the user has been using in this conversation. Default to English; if the user has been writing in Chinese / Japanese / Spanish / etc., translate the template headers, labels and prose accordingly. App / SKU / country names stay in their original form. The script itself emits English strings — translate them on the fly when rendering back into the conversation reply if the user's language is not English.

Top one-liner (required)

**Yesterday ({MM-DD}) revenue ${X}** · this week ${X} · this month ${X}

If Apple has not published a range's data yet, that slot shows N/A and the per-dimension block prints > ⏳ Data not yet published by Apple.

Totals block (5 dimensions, fixed order)

## 🧮 Totals

### {dimension} ({range-compact})

- 💰 Revenue: **{current revenue}**  ·  {↑↓ N%}
    1. **{revenue}** ({share}%)  ·  {↑↓ N%}  ·  {app name}
    2. **{revenue}** ({share}%)  ·  {↑↓ N%}  ·  {app name}
    3. **{revenue}** ({share}%)  ·  {↑↓ N%}  ·  {app name}
- 📥 Downloads: **{current downloads}**  ·  {↑↓ N%}
    1. **{downloads}** ({share}%)  ·  {↑↓ N%}  ·  {app name}
    2. **{downloads}** ({share}%)  ·  {↑↓ N%}  ·  {app name}
    3. **{downloads}** ({share}%)  ·  {↑↓ N%}  ·  {app name}

Footer note (required)

> ⓘ Revenue is multi-currency, converted to USD via approximate FX (not finance-grade). Apple daily reports lag 1–2 days.
> This month compares against the **entire previous month**; last 7/30 days compare against the 7/30 days before that.

10 inviolable rules

  1. Headings stay in a single language — match the user's conversation language; don't mix languages within a heading.
  2. No bar charts — change is shown only as ↑↓ N%.
  3. No "current X vs previous Y" — dates go only in the H3 heading parentheses.
  4. No "previous N" — show only the current value plus the percentage change.
  5. Keep indentation — the Top-3 list uses 4-space indentation, nested under the downloads/revenue bullet.
  6. Value first, app name last — {rank}. **{value}** ({share}) · {change} · {app name}.
  7. Revenue before downloads.
  8. App names keep their full original form, not truncated.
  9. Fixed emoji set: 📊 title / 🕐 time / 📅 date / 📱 app / 🧮 totals / 💰 revenue / 📥 downloads / ⏳ data not in / ⓘ note.
  10. Must paste back into the conversation — after running the script, Claude must paste the complete markdown report into the reply; "report.md generated" alone or a summary alone is not allowed.

Data handling details

  • Revenue: each row's Units × Developer Proceeds, converted to USD via a static 40+ currency FX table. This is an estimate (not accounting-grade — finance reconciliation uses /v1/financeReports), but cross-app relative comparison is reliable.
  • IAP merging: an IAP row's Title is the IAP product name; Parent Identifier is the parent app's SKU. IAP units go to iap_units; IAP revenue is folded into the app's revenue_usd.
  • Download classification (by Product Type Identifier): 1* / F1 / FI1 count as installs; 7* updates do not count; IA* IAP/subscription rows count toward revenue and iap_units but not downloads.
  • Sorting: Top-3 is descending by current downloads / revenue within each dimension.

CLI

# from the plugin repo root
python3 scripts/sales_report.py

No arguments. All logic runs automatically.

Known limits

  • Apple's daily sales reports lag 1-2 days (the script auto-anchors to the most recent day with data).
  • Revenue is converted via a static FX table (not a reconciliation value).
  • "This week" shows "data not in" early in the week before data arrives.
  • Multi-currency refunds (negative Units) are subtracted automatically but not highlighted separately.

Connection to other workflows

  • Upstream dependency: the appmate-setup skill's ASC API credentials.
  • Downstream: if an app's downloads/revenue drop sharply → trigger aso-daily-report to investigate the ASO side, or aso-optimize to redo the metadata.

Keep looking

Skills are one crate of 611,178. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.