- name
- asc-cli-usage
- description
- 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.
asc cli usage
Use this skill when you need to run or design asc commands for App Store Connect.
Command discovery
- Always use
--helpto discover commands and flags.asc --helpasc builds --helpasc builds list --help
- Use
asc searchfor 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 schemato 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 capabilitiesto explain CLI-supported, partial, web-session, and public-API-limited workflow coverage.asc capabilities --area release --output tableasc capabilities --status web-session --output tableasc capabilities --status not-public-api --output markdown
Prefer native commands over asc api
- Use a native command for every read and write. Find it with
asc search "TASK"or--helpbefore reaching forasc api. - For native reads that support
--include, use it to fetch related records in one call instead of one request per relationship. Use--output jsonto inspect related resources in theincludedarray.asc versions view --version-id "VERSION_ID" --include build,appStoreVersionSubmissionasc builds info --build-id "BUILD_ID" --include buildBetaDetail,betaAppReviewSubmission,betaGroupsasc iap view --id "IAP_ID" --include inAppPurchaseLocalizations,appStoreReviewScreenshotasc review submissions-get --id "SUBMISSION_ID" --include items,appStoreVersionForReview
- Single-resource and child-list reads have their own commands, such as , , and .