| name | appstore-connect |
| description | Interact with App Store Connect via the asc CLI - apps, builds, TestFlight, beta testers, reviews, sales/analytics, metadata, IAP, signing, submissions. Use for "check my app", "App Store Connect", "TestFlight status", "app review", "my app sales", or "asc". |
| disable-model-invocation | true |
App Store Connect (asc)
Read, manage, and ship any of the user's App Store apps through the asc CLI (App Store Connect CLI by Rork). asc covers nearly the entire ASC surface; reach for the raw API only for the rare gap.
`asc` is already authenticated on this machine (a default keychain profile). Verify before doing real work:
asc auth status
asc auth status --validate
asc doctor
- Multiple accounts/teams:
asc --profile <name> <command> selects a profile.
- A NEW account with no stored key: run the
find-asc-credentials skill (locates the .p8, key id, and issuer id, then asc auth login). Never print or commit .p8 keys, key ids, or issuer ids.
<how_to_drive>
Do NOT guess flags. asc is large and self-documenting — discover, then act:
asc --help
asc <area> --
asc docs list
- **Confirm before any mutation that is externally visible or hard to reverse:** `asc submit`, `asc publish ... --submit`, `asc review submit`, `asc pricing` changes, `asc iap`/`asc subscriptions` edits, `asc users` invites/removals, certificate/profile deletion. State the app id, version, and exact change, and get explicit user approval.
- Prefer dry runs / validation first: many commands accept `--dry-run`; always run `asc validate` before submitting.
- Never delete a signing certificate or provisioning profile without confirmation — it can break other apps signed with it.
- Never print or commit `.p8` keys, key ids, issuer ids, app-specific passwords, or downloaded financial reports with PII.
- This skill manages the store side only. Producing the build (.ipa/.aab) and project config belongs to the app's own deploy workflow.
