Asc Cli Usage
Run and design App Store Connect workflows with asc CLI—discovery, schemas, builds, versions, pricing, and release commands.
Overview
asc-cli-usage is an agent skill most often used in Launch (also Ship launch prep, Operate iterate) that guides asc CLI commands, discovery, and App Store Connect automation.
Install
npx skills add https://github.com/rorkai/app-store-connect-cli-skills --skill asc-cli-usageWhat is this skill?
- Discovery via asc --help, asc search, asc schema, and asc capabilities
- Canonical verbs: view (not legacy get) and edit for availability and pricing flows
- Schema inspection before POST/GET API-facing command design
- Capabilities matrix for public-API vs web-only workflow coverage
- Pagination, output formats, and auth patterns for repo automation
Adoption & trust: 713 installs on skills.sh; 845 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know the App Store workflow you need but not the exact asc command path, flags, or API limitations.
Who is it for?
Indie iOS developers automating App Store Connect from the terminal or CI in a repo that ships asc.
Skip if: Android Play Console workflows or marketers who only need copy advice without CLI or API access.
When should I use this skill?
User asks to run or design asc commands or interact with App Store Connect via the CLI.
What do I get? / Deliverables
You get correct, discoverable asc command sequences—with schema-backed fields and capability checks—for builds, versions, pricing, and release tasks.
- Documented asc command sequences
- Automation-ready flags and output format choices
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
App Store Connect operations are the canonical Launch shelf for getting iOS apps submitted, priced, and released. ASO and store metadata live alongside builds and review submission—the CLI spans listing and release mechanics.
Where it fits
List and verify uploaded builds before attaching a version for review submission.
Inspect app store version metadata and pricing availability before go-live.
Adjust availability or view release-related resources after a live incident or regional rollout.
How it compares
Operational CLI playbook for App Store Connect—not a replacement for Apple’s web UI where capabilities mark web-only coverage.
Common Questions / FAQ
Who is asc-cli-usage for?
Solo mobile builders and small teams using the asc CLI to manage builds, metadata, pricing, and submissions on App Store Connect.
When should I use asc-cli-usage?
At Launch for ASO and release automation; at Ship launch prep for build uploads and version checks; at Operate when iterating on live app store settings via CLI.
Is asc-cli-usage safe to install?
Review the Security Audits panel on this Prism page; CLI skills may imply network and API credentials—never commit secrets and scope keys minimally.
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.