app-store-connect
Skill0 starsChanged 30 days agoMITView on GitHub
App Store Connect API reference for the apple plugin — apps, builds, TestFlight groups/testers, App Store versions and review state, customer reviews, bundle IDs/certificates/profiles/devices, users, sales & finance reports, Xcode Cloud, Notary. Load for release management, TestFlight distribution, review replies, reports or any asc_* / notary_* tool.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- sesamehut/appstore-connect-skilltheir own version, first seen Jun 14, 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
- sesamehut/appstore-connect-skill★ 1same name
- sreejithraman/SreeStack★ 1same 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 repository15 other files it gives its agents.
- apnsSkill
- apple-business-managerSkill
- apple-mapsSkill
- apple-musicSkill
- apple-newsSkill
- apple-search-adsSkill
- apple-servicesSkill
- app-store-serverSkill
- cloudkitSkill
- docsSkill
- icloudSkill
- setupSkill
- sign-in-with-appleSkill
- statusSkill
- weatherkitSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
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
- Very specific: line 85
Prefer fields[...] to keep responses small.
“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 API (tools asc_*, notary_*)
Base https://api.appstoreconnect.apple.com; auth is an ES256 JWT (20 min) minted from
app_store_connect.key_id/issuer_id/private_key — handled by the server, cached 15 min.
Individual API keys (no issuer) are supported (sub: user). Permissions follow the key's role
(Admin, App Manager, Developer, Marketing, Finance, Sales, Customer Support).
JSON:API conventions (for asc_request)
- Filter:
filter[app]=123,filter[platform]=IOS,filter[processingState]=VALID. - Fields:
fields[builds]=version,uploadedDate(smaller responses). Include related:include=preReleaseVersion,include=app,build. - Sort:
sort=-uploadedDate; paging:limit=200max, followlinks.next(max_pages). - Writes:
{"data": {"type": "...", "attributes": {...}, "relationships": {...}}}withPOST(create),PATCH(update) andDELETE; relationship edits use/v1/<type>/<id>/relationships/<rel>with{"data": [{"type","id"}]}. - Rate limit header:
X-Rate-Limit: user-hour-lim:…;user-hour-rem:….
Common workflows
Find an app: asc_apps (filter by name/bundle id) → asc_app for versions, builds, groups.
Release status: asc_app_store_versions → appStoreState/appVersionState
(PREPARE_FOR_SUBMISSION, WAITING_FOR_REVIEW, IN_REVIEW, PENDING_DEVELOPER_RELEASE,
READY_FOR_SALE/READY_FOR_DISTRIBUTION, REJECTED, DEVELOPER_REJECTED). Attach a build to a version:
asc_request PATCH /v1/appStoreVersions/{id}/relationships/build body
{"data": {"type": "builds", "id": "<buildId>"}}. Submit for review: create
/v1/reviewSubmissions then /v1/reviewSubmissionItems, then PATCH submitted: true.
Release a pending version: PATCH /v1/appStoreVersions/{id} {"data":{"type":"appStoreVersions","id":"…","attributes":{"releaseType":"MANUAL"}}} then
POST /v1/appStoreVersionReleaseRequests.
Builds: asc_builds (processing: PROCESSING → VALID; expired builds can't be distributed).
Export compliance: PATCH /v1/builds/{id} usesNonExemptEncryption: false. What's new for
testers: POST /v1/betaBuildLocalizations.
TestFlight: asc_testflight_groups → asc_testflight_add_tester (external groups e-mail the
invite once the build passes beta review). Add a build to a group:
asc_request POST /v1/betaGroups/{id}/relationships/builds {"data":[{"type":"builds","id":"…"}]}.
Submit a build for beta review: POST /v1/betaAppReviewSubmissions. Public link: PATCH the
group publicLinkEnabled: true.
Customer reviews: asc_customer_reviews (sort -createdDate, filter rating/territory) →
asc_review_reply (one response per review; replying again replaces it).
Localizations / metadata: /v1/appStoreVersions/{id}/appStoreVersionLocalizations
(description, keywords, whatsNew, promotionalText), /v1/apps/{id}/appInfos →
/v1/appInfos/{id}/appInfoLocalizations (name, subtitle, privacy policy URL), screenshots via
appScreenshotSets/appScreenshots (upload needs the reservation + upload-operations flow).
Pricing & availability: /v1/apps/{id}/appPriceSchedule, /v1/appAvailabilities.
In-app purchases & subscriptions: /v1/apps/{id}/inAppPurchasesV2, /v1/apps/{id}/subscriptionGroups,
/v1/subscriptions/{id}/prices, promotional offers, introductory offers.
Signing: asc_signing kind=certificates|profiles|devices|bundle_ids; create a device:
POST /v1/devices {"attributes":{"name","platform":"IOS","udid"}}; register a bundle id:
POST /v1/bundleIds; profiles: POST /v1/profiles with bundleId/certificates/devices relationships.
Reports: asc_sales_report (DAILY SALES SUMMARY by default, TSV; needs vendor_number and a
Sales/Finance-capable key; data for a day is available the next day),
asc_finance_report (monthly, region code e.g. ZZ for all). Analytics reports:
POST /v1/analyticsReportRequests (accessType ONGOING) → /v1/analyticsReportRequests/{id}/reports
→ /v1/analyticsReports/{id}/instances → /v1/analyticsReportInstances/{id}/segments (download URLs).
Xcode Cloud: asc_xcode_cloud products|workflows|build_runs|build_run|actions|start;
artifacts/issues/test results via /v1/ciBuildActions/{id}/artifacts|issues|testResults.
Notary: notary_submissions, notary_submission (status Accepted/Invalid/Rejected + log JSON).
Uploading a new submission needs xcrun notarytool locally (S3 upload); this plugin reads status/logs.
Users & access: asc_users; invite: POST /v1/userInvitations.
Gotchas
- 401
NOT_AUTHORIZEDwith a valid key → the key was revoked, the clock is off, or the key belongs to another team. 403 → role too low, or new agreements to accept in App Store Connect. - 409 on writes → state conflict (e.g. version already has a build, build expired).
- Many list endpoints cap
limitat 200; usemax_pages. - Prefer
fields[...]to keep responses small;compact: truestripslinks. - Docs:
apple_docs_index technology=appstoreconnectapi query="<endpoint words>".
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.

