Asc Cli Usage
Equip your coding agent with canonical asc CLI patterns so you can list builds, manage TestFlight, submit for review, and poll release state without guessing flags or legacy command aliases.
Overview
asc-cli-usage is an agent skill most often used in Launch (also Ship and Operate) that documents how to discover, run, and design asc CLI commands for App Store Connect with canonical verbs, output formats, auth, and pag
Install
npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-cli-usageWhat is this skill?
- Four discovery paths: `--help`, `asc search`, `asc schema`, and `asc capabilities` with table or markdown output
- Canonical verb map: `view` over legacy `get`, plus `edit`, `submit`, `publish`, and `versions` with deprecated-alias war
- Output formats `table`, `json`, `markdown`, and `pretty` for CI logs versus automation parsing
- Auth via env vars or `asc auth login`, keychain on macOS, and required `--confirm` for destructive actions
- Pagination with `--paginate` or `--limit`/`--next`, plus JSON validation flags like `--strict` and `--offline` schema ch
- Four command-discovery mechanisms: `--help`, `asc search`, `asc schema`, and `asc capabilities`
- Four standard output formats: table, json, markdown, and pretty
- Five canonical verb areas: view, edit, submit, publish, and versions
Adoption & trust: 2.5k installs on skills.sh; 845 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need to interact with App Store Connect from the terminal or an agent, but asc command paths, deprecated aliases, flags, and pagination behavior are easy to get wrong and break release automation.
Who is it for?
Indie iOS or Mac developers automating TestFlight, build upload, review submission, or release polling via asc in local shells or CI.
Skip if: Teams shipping only Android or web with no App Store Connect footprint, or anyone expecting full ASC coverage without checking web-only gaps in `asc capabilities`.
When should I use this skill?
Use when asked to run or design asc commands or interact with App Store Connect via the CLI.
What do I get? / Deliverables
Your agent runs consistent asc commands with the right verbs, formats, auth, and safety flags—and can validate requests against bundled schemas before touching production App Store data.
- Correct asc command invocations with chosen output format and pagination
- Schema-checked request designs from `asc schema` before write operations
- Capability-gap notes from `asc capabilities` when a workflow is CLI-partial or web-only
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
App Store Connect is the primary distribution channel for indie iOS and Mac apps; this skill belongs on the Launch shelf because its workflows center on shipping binaries, metadata, and review submission through ASC. Distribution is the subphase where solo builders upload builds, configure TestFlight, and move versions toward public release—exactly what the asc command reference and canonical verbs document.
Where it fits
Run `asc review submit` with the documented prerequisite checklist before flipping a version to customer release.
Upload a CI artifact and list processing builds with `--paginate` and `table` output for a quick human-readable status check.
Use `asc versions` and `view` commands to inspect live versus editable version metadata before copy changes go to review.
Poll `asc builds list` with JSON output and interpret processing versus failed states when a build sticks in App Store Connect.
How it compares
Procedural asc CLI playbook for agents—not an MCP server and not a substitute for Xcode-only or Apple web consoles where the CLI marks workflows as not-public-api.
Common Questions / FAQ
Who is asc-cli-usage for?
Solo builders and small teams who ship Apple-platform apps and want their AI coding agent to run or design App Store Connect tasks through the asc CLI reliably.
When should I use asc-cli-usage?
Use it when asked to run or design asc commands: at Launch for distribution and TestFlight, during Ship for review submission checklists, and in Operate when polling build processing or diagnosing ASC command failures.
Is asc-cli-usage safe to install?
It is documentation-only procedural guidance; review the Security Audits panel on this Prism page and treat App Store Connect API keys and destructive `--confirm` actions with your normal secrets hygiene.
SKILL.md
READMESKILL.md - Asc Cli Usage
# 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-only, and public-API-limited workflow coverage. - `asc capabilities --area release --output table` - `asc capabilities --status not-public-api --output markdown` ## Canonical verbs (current asc) - Prefer `view` over legacy `get` aliases for read-only commands in docs and automation. - `asc apps view --id "APP_ID"` - `asc versions view --version-id "VERSION_ID"` - `asc pricing availability view --app "APP_ID"` - Prefer `edit` for update-only availability surfaces and other canonical edit flows. - `asc pricing availability edit --app "APP_ID" --territory "USA,GBR" --available true` - `asc app-setup availability edit --app "APP_ID" --territory "USA,GBR" --available true` - `asc xcode version edit --build-number "42"` - Keep `set` where the CLI intentionally models a higher-level replacement/configuration flow and `--help` still shows `set` as the canonical verb. ## 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 `--paginate` when the user wants all pages. ## Output formats - Output defaults are TTY-aware: `table` in interactive terminals, `json` when piped or non-interactive. - Use `--output table` or `--output markdown` only for human-readable output. - `--pretty` is only valid with JSON output. ## 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`. - `ASC_APP_ID` can provide a default 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`. ## Apple Ads - Use `asc ads --help` before choosing a command. - Apple Ads uses `asc ads auth`, `--ads-profile`, and `ASC_ADS_*` variables. It does not use App Store Connect API credentials. - Resolve org access with `asc ads acls --output json` unless the org ID is already known. - Most endpoint commands need `--org` or `ASC_ADS_ORG_ID`. - Body commands use `--file` with Apple Ads JSON payloads. Object endpoints need a JSON object. Bulk endpoints often need a JSON array. - Use `--paginate` only where help shows it. Reporting and selector payloads carry pagination inside the JSON file. - Destructive commands and bulk delete commands require `--confirm`. - For live mutation tests, create paused resources with a clear test name and delete the parent campaign when done. ## Timeouts - `ASC_TIMEOUT` / `ASC_TIMEOUT_SECONDS` control request timeouts. - `ASC_UPLOAD_TIMEOUT` / `ASC_UPLOAD_TIMEOUT_SECONDS` control upload timeouts.