What output format should I use for automation vs readability?

Default is minified JSON for automation. Use --output table or --output markdown for human readability; --pretty formats JSON in a readable way.

How do I fetch all pages of results?

Add --paginate to commands that support paging and handle data until there are no more pages.

How should I configure authentication defaults?

Prefer keychain login with 'asc auth login'. If that’s not available, supply credentials via environment variables (ASC_KEY_ID, ASC_ISSUER_ID, ASC_PRIVATE_KEY_PATH/ASC_PRIVATE_KEY/ASC_PRIVATE_KEY_B64) and optionally set ASC_APP_ID as a default.

asc-cli-usage

Scanned

npx machina-cli add skill rudrankriyam/app-store-connect-cli-skills/asc-cli-usage --openclaw

Files (1)

SKILL.md

1.2 KB

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

Flag conventions

Use explicit long flags (e.g., --app, --output).
No interactive prompts; destructive operations require --confirm.
Use --paginate when the user wants all pages.

Output formats

Default output is minified JSON.
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.

Timeouts

ASC_TIMEOUT / ASC_TIMEOUT_SECONDS control request timeouts.
ASC_UPLOAD_TIMEOUT / ASC_UPLOAD_TIMEOUT_SECONDS control upload timeouts.

Source

git clone https://github.com/rudrankriyam/app-store-connect-cli-skills/blob/main/skills/asc-cli-usage/SKILL.mdView on GitHub

Overview

Guides on running and designing asc commands for App Store Connect. It covers command discovery, flags, output formats, authentication, and timeouts to help you automate tasks via the CLI.

How This Skill Works

The skill explains using asc --help to discover commands, applying explicit long flags, and opting into pagination and specific output formats. It also outlines how to configure authentication (keychain vs env vars) and how to control timeouts for requests and uploads.

When to Use It

You need to run or script asc commands against App Store Connect (e.g., listing builds, downloads).
You are designing automation or CI workflows that interact with App Store Connect via asc.
You want to discover available commands and flags before executing a task using --help.
You need to fetch all pages of results, enabling --paginate for complete data.
You want to configure authentication and timeouts using keychain login or environment variables.

Quick Start

Step 1: Run 'asc --help' and 'asc <command> --help' to discover commands and flags.
Step 2: Authenticate with 'asc auth login' (or set ASC_KEY_ID, ASC_ISSUER_ID, ASC_PRIVATE_KEY* as needed).
Step 3: Run a sample command like 'asc builds list --app 123 --paginate --output table' to fetch and view data.

Best Practices

Always run commands with --help to discover available subcommands and flags.
Use explicit long flags (e.g., --app, --output) and avoid interactive prompts; use --confirm for destructive actions.
Enable --paginate when you need all pages and plan for rate limiting.
Choose output formats based on the audience: default minified JSON for automation; --output table/markdown for human review; --pretty with JSON when readability matters.
Prefer keychain auth via asc auth login; provide defaults via ASC_APP_ID and environment variables (ASC_KEY_ID, ASC_ISSUER_ID, ASC_PRIVATE_KEY_PATH/ASC_PRIVATE_KEY/ASC_PRIVATE_KEY_B64).

Example Use Cases

asc --help
asc builds list --help
asc builds list --app 123 --paginate --output table
asc auth login
asc apps delete --app 123 --confirm

Frequently Asked Questions

Add this skill to your agents