Back to 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.

803stars44forksUpdated 5/20/2026

Security Assessment

Low Risk(70/100)

Detected risks:

Secret Exposure([SKILL.md] PRIVATE_KEY)
Security Score70/100

About asc-cli-usage

The asc-cli-usage skill provides structured guidance for working with the `asc` command-line interface used to interact with App Store Connect within this repository. It is designed to help users correctly construct, interpret, and maintain consistent `asc` commands for reading and modifying App Store Connect resources. The skill focuses on standardizing command usage, improving discoverability, and reducing errors when working with CLI-based workflows.

This skill highlights key operational features of the `asc` CLI, including command discovery through `--help` at multiple levels (such as `asc --help` and subcommand help), and encourages the use of canonical verbs like `view` for read-only operations and `edit` for update workflows. It also documents flag conventions such as the preference for explicit long-form flags, the requirement of `--confirm` for destructive actions, and the use of `--paginate` for retrieving full multi-page results. Output handling is also standardized, with support for TTY-aware defaults, explicit output formats like table or markdown for readability, and JSON output for automation, including the constraint that `--pretty` only applies to JSON output.

In addition, the skill defines authentication and runtime behavior expectations, including keychain-based login via `asc auth login`, fallback environment variables for credentials, and optional defaults like `ASC_APP_ID`. It also outlines timeout controls for general requests and uploads using environment variables. Target users include developers, DevOps engineers, and release managers who automate App Store Connect workflows, manage app metadata, handle pricing and availability updates, and integrate `asc` into CI/CD pipelines. It is especially useful in environments where consistent CLI usage, predictable automation behavior, and secure authentication practices are required.

FAQ

How do I discover available asc CLI commands and flags?

You should use the built-in help system at multiple levels, such as `asc --help`, `asc builds --help`, or more specific subcommands like `asc builds list --help` to explore available commands and options.

What authentication methods does the asc CLI support?

The CLI prefers keychain-based authentication using `asc auth login`, but it can also fall back to environment variables such as ASC_KEY_ID, ASC_ISSUER_ID, ASC_PRIVATE_KEY_PATH, ASC_PRIVATE_KEY, and ASC_PRIVATE_KEY_B64.

When should I use --confirm in asc commands?

The `--confirm` flag is required for destructive operations to ensure they are explicitly acknowledged before execution.

How does asc handle output formatting?

Output is TTY-aware, defaulting to table format in interactive terminals and JSON in non-interactive environments. You can explicitly set formats like table or markdown, and use `--pretty` only with JSON output.

Install asc-cli-usage

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill