app-store-connect
Skill1 starsChanged 5 months agoMITView on GitHub
Operates Apple App Store Connect through a bundled CLI. Lists apps and App Store versions; reads and updates store metadata and localizations (description, keywords, what's new, promotional text, app name, subtitle, privacy policy); adds new locales; reads customer reviews and posts or replaces developer responses; downloads sales, finance, and analytics reports to disk; uploads, lists, reorders, and deletes App Store screenshots and preview videos; manages TestFlight beta groups, testers, test info, beta review detail and submission, and reads/downloads beta feedback; lists builds, resolves the latest processed build, edits build distribution and notes, and expires builds; runs an App Store submission-readiness preflight, sets review contact/demo detail, configures release timing and the export-compliance flag, reads submission status, and submits, cancels, or releases a version for App Review; verifies credentials against the live App Store Connect API. Use when the user asks about App Store Connect, ASC, app metadata, store listings, localization, customer reviews, review replies, sales or download numbers, finance reports, analytics, TestFlight, beta testers, beta groups, beta feedback, builds, App Store reports, screenshots, preview videos, submitting an app for review, App Review, release timing, export compliance, releasing a version, or checking that App Store Connect API credentials work.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- cpoder/claude-apple-plugintheir own version, first seen Nov 15, 2026
- beautyfree/appstore-connect-mcptheir own version, first seen Nov 15, 2026
- sreejithraman/SreeStacktheir own version, first seen Oct 27, 2026
- saif-o99/app-launch-skillstheir own version, first seen Oct 13, 2026
- LukaGiorgadze/openctotheir own version, first seen Jun 16, 2026
- nvm1410/claude-skillstheir own version, first seen Jun 12, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- beautyfree/appstore-connect-mcp★ 14same name
- 199-biotechnologies/app-store-connect-skill★ 11same name
- LukaGiorgadze/opencto★ 1same name
- sreejithraman/SreeStack★ 1same name
- cpoder/claude-apple-plugin★ 0same name
- nvm1410/claude-skills★ 0same name
- saif-o99/app-launch-skills★ 0same name
- sosteam65/app-store-connect-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- plugin/CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
All capabilities go through one CLI.
- Very specific: line 16
Every command and subcommand answers --help with its exact flags.
- Very specific: line 52
Run capabilities for the authoritative machine-readable map — do not guess.
- Distinctive: line 115
Default to hands-off: tell the user exactly what to paste where, and let them paste it.
- Distinctive: line 122
When the user picks a location, record that preference — the storage method only, never the key — to your memory, so a later setup skips …
- Very specific: line 136
Read more deliberately with --all or --max-items N.
- Very specific: line 338
before any request: groups delete, groups remove-testers, testers delete, testers remove-from-app, test-info delete, notes delete, groups …
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
App Store Connect
All capabilities go through one CLI. Never call the ASC HTTP API directly; run the CLI and parse its output.
node "${CLAUDE_SKILL_DIR}/../../../dist/cli/index.js" <domain> <verb> [flags]Every command and subcommand answers --help with its exact flags. When in
doubt, ask the command itself.
Capability boundary
Works now: apps (list/get), versions (list), metadata (app-level and
version-level localizations: list/get/update/add-locale), reviews
(list/get/get-response/respond), reports (sales/finance downloads, the
analytics report lifecycle and downloads), media (screenshots and preview
videos: list-sets/list/upload/upload-set/delete/delete-set/reorder/status),
testflight (groups
list/get/create/update/delete/testers/add-testers/remove-testers/builds/public-link/criteria/criteria-build-check;
testers list/get/create/bulk-add/delete/remove-from-app; test-info
list/set/delete; review-detail get/set; feedback
list-crashes/list-screenshots/get-crash/get-screenshot/download), builds
(list/get/latest/expire; beta-detail get/set; notes list/set/delete;
review status/submit; groups add/remove; testers list/add/remove;
pre-release-versions list), submission (preflight; status list/get;
review-detail get/set; release-config set; export-compliance set;
submit/cancel/release — high side effect, --force), doctor,
auth (check — one live read to confirm the credentials authenticate),
capabilities.
Not implemented here yet (the CLI answers these with exit code 5 and the planned milestone): nothing in the current first-party scope — every domain above is implemented. Deferred-but-Apple-supported writes (phased-release control, age-rating questionnaire, export-compliance declaration documents) are not exposed yet; tell the user they are planned, not that Apple lacks them.
Not possible via Apple's API (route the user to the App Store Connect
website): editing or deleting customer reviews or star ratings, App Review /
Resolution Center messages, agreements/tax/banking, creating or downloading
API keys, the legacy per-version submission model (Apple removed it — use
submission submit), editing a review submission's items after submit (cancel
and re-submit instead), and un-canceling a canceled submission.
Run capabilities for the authoritative machine-readable map — do not guess.
One-time setup
Credentials come from environment variables; never echo private key content, and never write them into a git-tracked file. The user supplies them — if they are missing, help the user set up (below) instead of giving up.
| Variable | Meaning |
ASC_KEY_ID | App Store Connect API key ID (required) |
ASC_ISSUER_ID | Issuer ID — set for team keys, omit for individual keys |
ASC_PRIVATE_KEY | The .p8 private key content, inline PEM |
ASC_PRIVATE_KEY_PATH | Path to the .p8 file (exactly one of the two key variables) |
ASC_VENDOR_NUMBER | Optional; needed for sales/finance report downloads (or pass --vendor) |
Keys are created in App Store Connect → Users and Access → Integrations. The vendor number is shown in App Store Connect → Payments and Financial Reports; the API cannot read it.
Build once after install or after CLI changes (paths are explicit so the working directory never matters):
npm ci --prefix "${CLAUDE_SKILL_DIR}/../../.."
npm run build --prefix "${CLAUDE_SKILL_DIR}/../../.."
node "${CLAUDE_SKILL_DIR}/../../../dist/cli/index.js" doctordoctor is offline and reports exactly what is missing and how to fix it (it
also warns when a Key ID and Issuer ID look swapped, or a private key looks
quoted or non-PEM). auth check is the online counterpart: one harmless read
that proves the credentials actually authenticate and the key's role can read.
Helping a user set up
A credentials error (exit 2, or a failing doctor credentials check) usually
means the user has not configured the key yet — walk them through it instead of
stopping:
- Get the values from the App Store Connect locations noted above —
Integrations for the keys and Issuer ID, Payments and Financial Reports for the
optional vendor number; the
.p8downloads once. Pick where the credentials live, then set them there. Offer the choice and the trade-off:
- User-level Claude Code settings
envblock (~/.claude/settings.json, or%USERPROFILE%\.claude\settings.json) — recommended: outside every git repo, so the key can't be committed by accident. - A project's gitignored
.claude/settings.local.jsonenvblock — per project; confirm it is ignored before committing. - Shell
export/$env:before launching — ephemeral, one session only.
ASC_PRIVATE_KEY_PATH(a path to the saved.p8) is simplest;ASC_PRIVATE_KEY(the.p8on one line) also works — set exactly one. A settingsenvchange needs a Claude Code restart to load.- User-level Claude Code settings
- Re-run
doctor, thenauth checkto confirm.doctorproves the variables are present and well-formed offline;auth checkproves they actually authenticate against Apple. A 401 there usually means a wrong or revoked key (or, for a non-coder, an inaccurate computer clock); a 403 means the key's role is too narrow — note that a non-Admin user can self-generate an individual key under Users and Access → Integrations without needing the account holder.
Default to hands-off: tell the user exactly what to paste where, and let them
paste it. You MAY write the file for them, but only after saying out loud that the
private key will sit as plaintext on disk and getting explicit consent — and even
then write only to a non-tracked file (user-level settings, or a gitignored
.claude/settings.local.json), never a git-tracked file such as a project's
shared .claude/settings.json, and never print the key back into the conversation.
When the user picks a location, record that preference — the storage method
only, never the key — to your memory, so a later setup skips the question. Do not
record "setup done": whether credentials exist is always a live doctor check,
not memory (a stale note misleads across machines and projects).
Reading output
- stdout carries only the JSON result envelope:
{ ok, command, data, pagination?, rateLimit?, resolved? }. On failure stdout is empty — parse it only when the exit code is 0. - stderr carries diagnostics:
error[<category>]: ...followed by ahint:line with the next action. - List reads default to a single page.
pagination.truncated: truemeans more data exists — always relaytruncated/totalhonestly to the user. Read more deliberately with--allor--max-items N. resolvedreports intermediate resources the CLI picked for you (e.g. which appInfo ametadata appcommand targeted).
Exit codes:
| Code | Meaning | Next action |
| 0 | success | parse stdout |
| 1 | unexpected failure | inspect stderr; report a bug |
| 2 | credentials / configuration | fix env vars; run doctor |
| 3 | ASC request error (auth, permission, not-found, invalid input, upstream, network) | read error[<category>] and the hint |
| 4 | rate limit (real 429 or proactive safety floor) | stop; wait or narrow the read |
| 5 | not implemented in this project yet | tell the user the planned milestone; do not retry |
| 6 | not supported by Apple's API | route the user to the ASC website |
| 64 | usage error | fix the command line per --help |
Task routing
| Task | Command |
| Check the environment (offline) | doctor |
| Confirm credentials work against Apple (live) | auth check |
| Find an app | apps list --bundle-id com.example.app |
| Read app details | apps get <appId> |
| List versions / find the editable one | versions list --app <appId> --state PREPARE_FOR_SUBMISSION |
| Read version metadata for a locale | metadata version get --version <versionId> --locale en-US |
| List a version's locales | metadata version list --version <versionId> |
| Update store description / keywords / what's new | metadata version update --version <versionId> --locale en-US --description "..." |
| Update promotional text (works on the live version) | metadata version update --version <versionId> --locale en-US --promotional-text "..." |
| Add a language to a version | metadata version add-locale --version <versionId> --locale fr-FR --description "..." |
| Read app name / subtitle | metadata app get --app <appId> --locale en-US |
| Change app name / subtitle | metadata app update --app <appId> --locale en-US --subtitle "..." |
| Add an app-level language | metadata app add-locale --app <appId> --locale fr-FR --name "..." |
| List reviews | reviews list --app <appId> --sort -createdDate |
| Reviews still needing a reply | reviews list --app <appId> --unanswered |
| Read one review (with the reply) | reviews get <reviewId> --include-response |
| Read the existing reply | reviews get-response --review <reviewId> |
| Reply to a review (creates or replaces) | reviews respond --review <reviewId> --body-file reply.txt |
| Download a day's sales report | reports sales download --date 2026-06-10 |
| Download a monthly finance report | reports finance download --region ZZ --date 2026-05 |
| Set up analytics reports (one-time) | reports analytics ensure-request --app <appId> |
| See which analytics reports exist | reports analytics list-reports --request <requestId> |
| Download an analytics report | reports analytics download --app <appId> --name "App Downloads Standard" |
| Upload one screenshot | media screenshots upload --version <versionId> --locale en-US --display-type APP_IPHONE_67 --file shot.png |
| Upload a folder of screenshots | media screenshots upload-set --version <versionId> --locale en-US --display-type APP_IPHONE_67 --dir ./shots --reorder |
| List a version's screenshot sets | media screenshots list-sets --version <versionId> --locale en-US |
| List a set's screenshots | media screenshots list --set <setId> |
| Reorder a set | media screenshots reorder --set <setId> --order id1,id2,id3 |
| Remove a screenshot / clear a stuck upload | media screenshots delete <screenshotId> |
| Check a screenshot's processing | media screenshots status <screenshotId> --wait |
| Upload one preview video | media previews upload --version <versionId> --locale en-US --preview-type IPHONE_67 --file clip.mov |
| List beta groups | testflight groups list --app <appId> |
| Read one beta group | testflight groups get <groupId> --include app,builds,betaTesters |
| Create a beta group | testflight groups create --app <appId> --name "Internal" --internal |
| Update a beta group | testflight groups update <groupId> --name "..." --feedback |
| Delete a beta group | testflight groups delete <groupId> --force |
| List a group's testers | testflight groups testers <groupId> |
| Add testers to a group (emails invites) | testflight groups add-testers <groupId> --testers id1,id2 --force |
| Remove testers from a group | testflight groups remove-testers <groupId> --testers id1,id2 --force |
| List a group's builds | testflight groups builds <groupId> |
| Enable/disable a public link (exposes the app) | testflight groups public-link <groupId> --enable --force |
| Read/set/clear recruitment criteria | testflight groups criteria set <groupId> --filter IPHONE:15.0:17.0 |
| List the recruitment-criteria matrix | testflight groups criteria options |
| Preflight a group's compatible build | testflight groups criteria-build-check <groupId> |
| List beta testers | testflight testers list --app <appId> |
| Read one tester | testflight testers get <testerId> --include apps,betaGroups |
| Create a tester (may email an invite) | testflight testers create --email a@x.com --group <groupId> --force |
| Add many testers by email to a group | testflight testers bulk-add --group <groupId> --emails-file emails.txt --force |
| Delete a tester (account level) | testflight testers delete <testerId> --force |
| Remove a tester from apps | testflight testers remove-from-app <testerId> --app id1,id2 --force |
| List app-level TestFlight metadata | testflight test-info list --app <appId> |
| Set TestFlight metadata for a locale | testflight test-info set --app <appId> --locale en-US --description "..." |
| Delete a TestFlight metadata locale | testflight test-info delete <localizationId> --force |
| Read beta review contact/demo info | testflight review-detail get --app <appId> |
| Set beta review contact/demo info | testflight review-detail set <detailId> --contact-email a@x.com |
| List crash feedback | testflight feedback list-crashes --app <appId> |
| List screenshot feedback | testflight feedback list-screenshots --app <appId> |
| Read one crash (with the log text) | testflight feedback get-crash --id <submissionId> --with-log |
| Read one screenshot submission | testflight feedback get-screenshot --id <submissionId> |
| Download feedback attachments to disk | testflight feedback download --app <appId> --kind both --output ./feedback |
| List builds | builds list --app <appId> --processing-state VALID |
| Read one build | builds get <buildId> --include preReleaseVersion |
| Resolve the latest processed build | builds latest --app <appId> |
| Expire a build (irreversible) | builds expire <buildId> --force |
| Read a build's beta states | builds beta-detail get <buildId> |
| Set a build's auto-notify | builds beta-detail set <buildId> --auto-notify true |
| List/set a build's "what to test" notes | builds notes set <buildId> --locale en-US --whats-new "..." |
| Delete a build note locale | builds notes delete <localizationId> --force |
| Read a build's beta review status | builds review status <buildId> |
| Submit a build for beta review (real review) | builds review submit <buildId> --force |
| Distribute a build to groups | builds groups add <buildId> --group id1,id2 --force |
| Stop distributing a build to groups | builds groups remove <buildId> --group id1,id2 --force |
| List/add/remove a build's individual testers | builds testers add <buildId> --tester id1,id2 --force |
| List pre-release (train) versions | builds pre-release-versions list --app <appId> |
| Check if a version is ready to submit | submission preflight --version <versionId> |
| List a version's review submissions | submission status list --app <appId> |
| Read one review submission | submission status get <submissionId> --include app,items,appStoreVersionForReview |
| Read a version's App Review contact/demo detail | submission review-detail get --version <versionId> |
| Set a version's App Review contact/demo detail | submission review-detail set --version <versionId> --contact-email a@x.com |
| Configure release timing (manual/scheduled) | submission release-config set --version <versionId> --release-type MANUAL |
| Attach/swap a build on a version | submission release-config set --version <versionId> --build <buildId> |
| Set a build's export-compliance flag | submission export-compliance set --build <buildId> --uses-non-exempt-encryption false |
| Submit a version for App Review (real review) | submission submit --version <versionId> --force |
| Cancel/withdraw a review submission (forces re-review) | submission cancel <submissionId> --force |
| Release an approved version to the public now | submission release --version <versionId> --force |
media previews mirrors media screenshots, swapping --display-type for
--preview-type (and upload adds optional --mime-type / --frame-time-code).
Conventions
- Ids come from prior list commands; never invent them.
- Locales are BCP-47 (
en-US,de-DE). - For multi-line or quoted text, write it to a file and use
--from-json file.json(metadata) or--body-file file.txt(review replies) instead of inline flags — this avoids shell quoting issues, especially on Windows. - In
--from-json, a JSONnullclears a field; an omitted key leaves it unchanged. metadata appwrites target the editable appInfo automatically; pass--liveto read the live one, or--app-info <id>to target explicitly.- Most version metadata is writable only while the version is editable
(e.g.
PREPARE_FOR_SUBMISSION);promotional-textis writable any time. ASTATE_ERRORon exit 3 means the target was not editable. reviews respondreplaces any existing response and publishes asynchronously (state starts asPENDING_PUBLISH).- Report downloads write files to disk; the envelope's
data.file(ordata.segmentsfor analytics) carries the path, row count, and headers — always relay the on-disk path to the user.--format jsonadditionally writes a JSON conversion next to the raw TSV/CSV. - Sales/finance
--outputis a single file path, not a folder; omit it to auto-name the file in the working directory, or pass a full path to place it. Analyticsdownloadinstead takes--output-dir(a folder for its segment files). To drop a sales/finance report into a specific folder, join your own filename onto that folder for--output. - The sales
--dateformat follows--frequency: DAILY/WEEKLY use YYYY-MM-DD (weekly = the week's closing date), MONTHLY uses YYYY-MM, YEARLY uses YYYY; omit the date for the latest report. The finance--dateis Apple's FISCAL month (YYYY-MM), which shifts against the calendar. - Analytics reports need a one-time
ensure-requestper app; Apple generates the first data 1-2 days later (the catalog of report names appears immediately, dated instances follow). Iflist-requestsshowsstoppedDueToInactivity: true, runensure-requestagain — it creates a fresh request and reports the stopped ones. - A sales/finance 404 usually means the report does not exist for that date/frequency (timing or no activity), not a wrong id — the error message carries the availability rules.
mediaupload addresses a localization by--version <id> --locale <code>; the CLI resolves it and finds-or-creates the set for the--display-type/--preview-type(resolved.setCreatedreports which).--display-typeand--preview-typeare device classes (run--helpfor the list); the values are the same ones Apple's API uses.- Upload reserves, transfers the bytes to Apple's short-lived signed URL
(never logged, never in the envelope), commits a checksum, then blocks until
Apple finishes processing.
--no-waitreturns right after the commit;status <id>(optionally--wait) resumes the check. A poll timeout is a success withresolved.pollTimedOut: true, not a failure — the bytes are up. - Upload appends to a set (Apple allows several per device class); it does
not replace.
upload-setuploads a folder in filename order and, with--reorder, makes that batch lead the set. Remove extras or a stuck reservation withdelete. - A
file-processingexit 3 names the stage in stderr:transfer(the PUT failed — re-run for fresh upload URLs),commit(checksum rejected), orprocessing(Apple rejected the asset's dimensions/format — the state errors say why).delete-setneeds--forcewhen the set still holds assets. - TestFlight invitations are real emails.
testflight groups add-testers,testflight testers create --group,testflight testers bulk-add, andbuilds testers addemail real TestFlight invitations to real people. They all require--force. Confirm the recipients with the user first; an invite cannot be unsent. - Submitting a build for beta review triggers a real Apple review.
builds review submit <buildId> --forcestarts an external TestFlight beta review; the submission cannot be patched or deleted (a rejection needs a fresh submit). Never run it speculatively. builds expireis irreversible. Apple's API has no un-expire; an expired build leaves testing for good. Requires--force.- Submitting a version for App Review starts a real, public review.
submission submit --version <versionId> --forceopens a modern review submission and PATCHes it submitted — this triggers a REAL Apple App Review of the live store listing. Runsubmission preflightfirst and confirm with the user; never submit speculatively. The call is async-accept (the envelope reportsaccepted, not a final state). - Releasing a version goes public immediately and cannot be undone.
submission release --version <versionId> --forcereleases an approved (MANUAL, pending-developer-release) version to the public right away. There is no un-release. Confirm with the user first. - Canceling a review submission forces a fresh review.
submission cancel <submissionId> --forcewithdraws a submission; the version flips to Developer Rejected, accepted items must be re-submitted, and re-review starts from scratch. A canceled submission cannot be un-canceled. - The three
submissionhigh-side-effect verbs —submit,cancel,release— require--force(a missing--forceis exit 64 before any request). They are never run by the smoke check; treat them like the other irreversible actions and confirm with the user. - The legacy per-version submission model (
appStoreVersionSubmissionscreate/ read) is not supported by Apple's API (exit 6) — Apple removed it. Usesubmission submit/status/preflightinstead. Editing a submission's items after submit is also unsupported (cancel and re-submit); un-canceling is too. - Enabling a public link exposes the app.
testflight groups public-link --enable(andcreate --public-link) opens public external recruitment — a real exposure, no per-person email — and requires--force. - Destructive deletes/removes need
--force, raised as a usage error (exit 64) before any request:groups delete,groups remove-testers,testers delete,testers remove-from-app,test-info delete,notes delete,groups criteria clear,builds groups remove,builds testers remove,builds expire. - Feedback download writes files to disk and the path is relayed.
testflight feedback download --output <dir>writes crash logs and screenshots into the directory; the envelope'sdata.submissions[].savedFilescarries the on-disk paths — relay them to the user. Downloads continue on error (an expired signed URL records an item-levelerrorand the batch proceeds). - The envelope never contains a signed attachment URL. Screenshot feedback
carries short-lived signed URLs that are secrets; the CLI fetches the bytes
for you (
download) and only ever reports on-disk paths, byte counts, width/height,expirationDate, and a de-queriedsanitizedUrl. Never try to fetch a signed URL yourself — usedownload. - TestFlight reads default to a single page like every list; relay
pagination.truncated/totalhonestly. A not-found ontestflight review-detail getmeans no beta review detail exists for that app yet, not a wrong id. - A group's
--internal/--all-buildsare fixed at creation;groups updaterejects them (exit 64). Recruitment--filterisdeviceFamily:minOs:maxOs(OS bounds optional), repeatable; runtestflight groups criteria optionsfor the legal device-family/OS matrix.
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
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.

