Guidance for using asc cli in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.
SKILL.md
asc cli usage
Use this skill when you need to run or design asc commands for App Store Connect.
Command discovery
Always use --help to discover commands and flags.
asc --help
asc builds --help
asc builds list --help
Use asc search for local, deterministic command discovery when you know the workflow but not the command path.
asc search "submit app for review"
asc search --output table "upload build"
Use asc schema to inspect bundled App Store Connect endpoint schemas and request/query fields before designing API-facing commands.
asc schema --pretty "GET /v1/apps"
asc schema --method POST appStoreVersions
Use asc capabilities to explain CLI-supported, partial, web-session, and public-API-limited workflow coverage.
Use asc pricing availability create to initialize app availability before using the update-only edit command. If Apple rejects the public-API bootstrap, authenticate a web session and use asc web apps availability create, or configure Pricing and Availability in App Store Connect.
Apple Ads uses asc ads auth, --ads-profile, and ASC_ADS_* variables. It does not use App Store Connect API credentials.
Direct resource commands use Platform API v1 with --ad-account or ASC_ADS_AD_ACCOUNT_ID. Deprecated Campaign Management API v5 commands live under asc ads v5 and use --org or ASC_ADS_ORG_ID; never substitute one ID for the other.
Discover ad-account access with asc ads auth discover --output json or inspect one ACL response with asc ads acls list --output json.
Body commands use --file with the exact schema named by the leaf help. V1 query filters use singular value, and bulk bodies may use wrapper objects rather than v5 arrays.
Apple Ads resource commands emit JSON. Use --paginate only where help shows it; reports and most query bodies carry pagination inside the JSON file.
Deletes and spend-, billing-, delivery-, targeting-, or access-sensitive mutations require --confirm. An explicitly paused campaign create is the main documented safe exception.
For live mutation tests, create paused resources with a clear test name, save every ID, pause spend-bearing resources first, and delete only resources created by the test.
Timeouts
ASC_TIMEOUT / ASC_TIMEOUT_SECONDS control request timeouts.
ASC_UPLOAD_TIMEOUT / ASC_UPLOAD_TIMEOUT_SECONDS control upload timeouts.
