App Store Connect

Use this umbrella skill as the entry point for App Store Connect work. It is a routing and safety guide; the detailed workflows live in references/<skill-name>/SKILL.md.

Do not load every reference by default. Classify the task, read the relevant reference skills, then execute with the current local asc command surface.

1. Install

• brew install asc - Homebrew (recommended)
• curl -fsSL https://asccli.sh/install | bash - Install script (macOS/Linux)

2. Authenticate

asc auth login \
  --name "MyApp" \
  --key-id "ABC123" \
  --issuer-id "DEF456" \
  --private-key /path/to/AuthKey.p8 \
  --network

Generate API keys at: https://appstoreconnect.apple.com/access/integrations/api

If you are running in CI, a headless shell, or a machine where keychain access is not available, use config-backed auth instead:

asc auth login \
  --bypass-keychain \
  --name "MyCIKey" \
  --key-id "ABC123" \
  --issuer-id "DEF456" \
  --private-key /path/to/AuthKey.p8

3. Validate auth

asc auth status --validate
asc auth doctor

First command

asc apps list --output table
asc apps list --output json --pretty

Core Workflow

1. Identify the goal: build, beta, metadata, submission, pricing, diagnostics, app creation, signing, or automation.
2. Read references/asc-cli-usage/SKILL.md before designing or running non-trivial asc commands.
3. Read references/asc-id-resolver/SKILL.md when any command needs app, version, build, group, tester, subscription, IAP, or review IDs.
4. Read the task-specific reference skills from the map below.
5. Prefer JSON output for automation and table/markdown output for user-facing checks.
6. Validate or dry-run before remote writes whenever the command supports it.
7. Verify the resulting App Store Connect state before reporting success.

Reference Map

Common Routes

For a new app from source, usually read:

1. asc-cli-usage
2. asc-signing-setup
3. asc-app-create-ui if the App Store Connect app record does not exist
4. asc-xcode-build
5. asc-metadata-sync
6. asc-shots-pipeline or asc-screenshot-resize
7. asc-submission-health and asc-release-flow

For a normal App Store release, usually read:

1. asc-id-resolver
2. asc-xcode-build
3. asc-build-lifecycle
4. asc-metadata-sync or asc-whats-new-writer
5. asc-release-flow
6. asc-submission-health

For a beta rollout, usually read:

1. asc-id-resolver
2. asc-xcode-build if a new build is needed
3. asc-build-lifecycle
4. asc-testflight-orchestration
5. asc-crash-triage after testers have feedback or crashes

For store listing work, usually read:

1. asc-metadata-sync
2. asc-localize-metadata for translations
3. asc-aso-audit for keyword and ASO checks
4. asc-whats-new-writer for release notes
5. asc-screenshot-resize or asc-shots-pipeline for screenshots

For monetization work, usually read:

1. asc-id-resolver
2. asc-ppp-pricing
3. asc-subscription-localization
4. asc-revenuecat-catalog-sync when RevenueCat is involved
5. asc-release-flow for first-review subscription or IAP blockers

For macOS distribution outside the App Store, read asc-notarization. For macOS App Store submission, use asc-xcode-build, then asc-release-flow and asc-submission-health.

Safety Rules

• Treat App Store Connect operations as production operations.
• Confirm authentication context before writes: asc auth status or the relevant ASC_* environment.
• Use explicit long flags and deterministic IDs. Avoid relying on "latest" unless the user explicitly wants it or the reference says it is safe.
• Use --paginate for list commands that feed automation.
• Use --dry-run, validation, or preview commands before changing metadata, pricing, submissions, workflows, screenshots, RevenueCat mappings, or signing assets.
• Require explicit user approval before review submission, app creation final click, price changes, certificate/profile revocation, build expiration, RevenueCat writes, privacy publish, or other hard-to-undo mutations.
• Never store App Store Connect browser cookies. Browser UI automation must use a visible local session and allow the user to complete login and 2FA.
• Treat asc web ... commands as experimental web-session escape hatches for gaps in the public API. Offer a manual fallback when appropriate.
• Do not claim success from command completion alone. Verify by reading the resulting App Store Connect state.

Verification

Use the most specific verification available:

• Builds: asc builds info --build-id "BUILD_ID" and confirm processing/validity.
• Metadata: asc metadata validate, asc metadata push --dry-run, then read/list the edited fields.
• Screenshots: asc screenshots validate and list uploaded screenshots after upload.
• TestFlight: list groups/testers/build attachments after distribution.
• Submissions: asc validate, asc status, asc submit status, or review submission list/detail commands.
• Pricing: pricing summary or schedule views before and after apply.
• RevenueCat sync: re-read ASC and RevenueCat catalogs and report created/skipped/failed items.
• Notarization: status/log commands, then staple verification when stapling.

Notes

• This skill pack is for the unofficial community asc CLI and is not affiliated with Apple.
• Always check --help for exact flags because the CLI evolves.
• Prefer the current canonical release path: asc validate, asc release stage, asc review submit, and asc publish appstore.
• Do not use removed legacy submission shortcuts when the reference skills say they are obsolete.