Asc Cli Usage
Discover and run asc CLI commands for App Store Connect—auth, pagination, schemas, and release workflows—from your repo or agent terminal.
Overview
asc-cli-usage is an agent skill most often used in Launch (also Validate scope and Ship launch prep) that teaches asc CLI discovery, schemas, capabilities, and canonical App Store Connect commands.
Install
npx skills add https://github.com/rudrankriyam/asc-skills --skill asc-cli-usageWhat is this skill?
- Discovery-first workflow: asc --help, subcommand help, and asc search for deterministic command lookup
- asc schema --pretty for GET/POST field inspection before automation
- asc capabilities with --area release and not-public-api status for coverage gaps
- Canonical verbs: prefer view over legacy get, edit for pricing availability updates
- Output formats and pagination guidance for scriptable ASC automation
- Documents 4 discovery surfaces: --help, search, schema, capabilities
- Canonical verb pair: view and edit over legacy get
Adoption & trust: 1.1k 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 cannot find the right asc subcommand, flags, or API limits for automation.
Who is it for?
Indie developers and small teams shipping iOS apps who automate TestFlight, metadata, and pricing via asc instead of clicking through the web UI.
Skip if: Android Play Console workflows, pure Swift in-app code, or marketers who never touch CLI or API tokens.
When should I use this skill?
Asked to run or design asc commands or interact with App Store Connect via the CLI.
What do I get? / Deliverables
You run documented asc search, schema, and capabilities flows then execute view/edit commands with correct output formats for CI or agent scripts.
- Correct asc command sequences with flags
- Schema-informed API field choices
- Capabilities-aware release automation plan
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Launch ASO is the primary shelf because asc drives App Store metadata, builds, pricing visibility, and review submission—the post-build distribution surface. ASO aligns with App Store Connect operations: versions, pricing availability, capabilities matrix, and review-oriented commands rather than in-app UI coding.
Where it fits
Use asc capabilities to see which release steps must stay manual before committing to a launch timeline.
List builds and pick upload targets with paginated asc builds list output.
Run asc search for submit-for-review then view app and version records with canonical view verbs.
Edit pricing availability after a price test without relearning deprecated get aliases.
How it compares
Operational asc CLI playbook—not Fastlane Ruby lanes and not an MCP wrapper around App Store Connect.
Common Questions / FAQ
Who is asc-cli-usage for?
Solo builders and agent users in repos that already use asc for App Store Connect who need consistent command discovery and verb conventions.
When should I use asc-cli-usage?
At Validate when scoping release steps; at Ship launch prep for build lists; at Launch for submit-for-review, pricing availability view/edit, and capabilities checks.
Is asc-cli-usage safe to install?
Review Security Audits on this page; asc commands use your App Store Connect credentials—limit agent permissions and rotate API keys used for auth.
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.