agentleFS
PawelBednarekPunksPawelBednarekPunks/aidevbird-skills/skills/appstore-payouts-to-excel/SKILL.md

appstore-payouts-to-excel

Skill1 starsChanged 8 days agoMITView on GitHub

Turn App Store Connect financial or sales reports into an Excel workbook with proceeds by currency, country and app, converted at NBP or given rates. Use for App Store income, payouts or bookkeeping.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use one kind per period; mixing both counts the same sales twice.

    line 11
  2. Distinctive:

    Run (path relative to this skill):

    line 13
  3. Distinctive:

    No rate flag: amounts stay in original currencies.

    line 21
  4. Distinctive:

    Check before handing over:

    line 30
  5. Very specific:

    Run xlsx-toolkit's inspect_xlsx.py on the output: no errors.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

App Store Payouts to Excel

Input — ask the user to download from App Store Connect (never sign in for them):

  • Payments and Financial Reports → one month, all regions (.txt, tab-separated). Use these for bookkeeping: they match what Apple pays.
  • Sales and Trends → Summary Sales report (.txt.gz). Use only for quick estimates — not final amounts. Use one kind per period; mixing both counts the same sales twice.

Run (path relative to this skill):

python scripts/appstore_to_xlsx.py payouts-2026-10.xlsx reports/*.txt --nbp 2026-11-05
  • --nbp DATE: NBP table A mid rates from the last business day before DATE (the common Polish rule for income in foreign currency; DATE = the income date the accountant uses, usually the invoice or payment date).
  • --rates rates.json --currency EUR: own rates ({"USD": 0.86}) to any currency.
  • No rate flag: amounts stay in original currencies; the Rates sheet lists what to fill in.

The script prints one JSON line: rows, totals per currency, rates, warnings. Act on every warning (unknown file, missing rate, mixed report kinds).

Workbook:

  • Summary: proceeds by currency, by country, by app — SUMIFS formulas, so they update when Data or Rates change.
  • Data: one row per report line; refunds are negative.
  • Rates: one rate per currency with its source. Edit here, not in Summary.

Check before handing over:

  1. Per-currency totals match the report footers (Total_Amount) or the payment shown in App Store Connect. If not, say which currency differs.
  2. Run xlsx-toolkit's inspect_xlsx.py on the output: no errors.

Report: totals per currency, total in the target currency with the rate date, and warnings. Hard rules: never alter report numbers; tax and VAT treatment (e.g. Apple's self-billing, reverse charge) is for the user's accountant — mention it, don't decide it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.