App-store-connect-cli-skills asc-cli-usage
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.
install
source · Clone the upstream repo
git clone https://github.com/rorkai/app-store-connect-cli-skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/rorkai/app-store-connect-cli-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/asc-cli-usage" ~/.claude/skills/rorkai-app-store-connect-cli-skills-asc-cli-usage && rm -rf "$T"
manifest:
skills/asc-cli-usage/SKILL.mdsource content
asc cli usage
Use this skill when you need to run or design
asc commands for App Store Connect.
Command discovery
- Always use
to discover commands and flags.--helpasc --helpasc builds --helpasc builds list --help
Canonical verbs (current asc)
- Prefer
over legacyview
aliases for read-only commands in docs and automation.getasc apps view --id "APP_ID"asc versions view --version-id "VERSION_ID"asc pricing availability view --app "APP_ID"
- Prefer
for update-only availability surfaces and other canonical edit flows.editasc pricing availability edit --app "APP_ID" --territory "USA,GBR" --available trueasc app-setup availability edit --app "APP_ID" --territory "USA,GBR" --available trueasc xcode version edit --build-number "42"
- Keep
where the CLI intentionally models a higher-level replacement/configuration flow andset
still shows--help
as the canonical verb.set
Flag conventions
- Use explicit long flags (e.g.,
,--app
).--output - Prefer explicit flags in automation; some newer commands can prompt for missing fields when run interactively.
- Destructive operations require
.--confirm - Use
when the user wants all pages.--paginate
Output formats
- Output defaults are TTY-aware:
in interactive terminals,table
when piped or non-interactive.json - Use
or--output table
only for human-readable output.--output markdown
is only valid with JSON output.--pretty
Authentication and defaults
- Prefer keychain auth via
.asc auth login - Fallback env vars:
,ASC_KEY_ID
,ASC_ISSUER_ID
,ASC_PRIVATE_KEY_PATH
,ASC_PRIVATE_KEY
.ASC_PRIVATE_KEY_B64
can provide a default app ID.ASC_APP_ID- When permissions are unclear, inspect exact API key role coverage with
.asc web auth capabilities- This lives under the experimental web auth surface.
- It can resolve the current local auth by default, or inspect a specific key with
.--key-id
Timeouts
/ASC_TIMEOUT
control request timeouts.ASC_TIMEOUT_SECONDS
/ASC_UPLOAD_TIMEOUT
control upload timeouts.ASC_UPLOAD_TIMEOUT_SECONDS