asc-cli-usage_skill

This skill helps you design and execute asc cli commands efficiently by guiding discovery, flags, outputs, and authentication best practices.

23

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

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

SKILL.md1.2 KB

Overview

This skill provides concise guidance for using the App Store Connect CLI (asc) to discover commands, set flags, handle output formats, manage authentication, and control pagination and timeouts. It is intended to help design and run asc commands reliably and reproducibly. Use it when you need clear rules and defaults for scripting or interactive use of the asc tool.

How this skill works

The skill outlines how to discover commands with --help, which flags to prefer, and when to use pagination and confirmation flags. It explains output modes (JSON, table, markdown), authentication methods (keychain or environment variables), and how to configure request and upload timeouts. Apply these rules to craft asc commands that are predictable and script-friendly.

When to use it

Designing asc commands for automation or CI pipelines
Running asc interactively and wanting safe, non-destructive defaults
Needing all pages of results from list endpoints
Determining which auth method to use for local vs CI environments
Choosing output formats for machine parsing or human review

Best practices

Use --help to discover available subcommands and flags before running a command
Prefer explicit long flags like --app and --output to avoid ambiguity
Avoid interactive prompts; require --confirm for destructive actions
Use --paginate to retrieve all pages when listing resources
Authenticate with asc auth login where possible and fall back to env vars for CI
Keep JSON as the default output for machine consumption; use --pretty only with JSON

Example use cases

List all builds for an app non-interactively: asc builds list --app <APP_ID> --paginate --output json
Generate a human-readable summary: asc builds list --app <APP_ID> --output table
Set CI credentials via env vars: export ASC_KEY_ID=... ASC_ISSUER_ID=... ASC_PRIVATE_KEY_PATH=...
Upload with extended timeout: export ASC_UPLOAD_TIMEOUT_SECONDS=600 and run asc upload command
Perform a destructive action safely: asc apps delete --app <APP_ID> --confirm

FAQ

Use --paginate when you need the full set of results across pages instead of the default single-page response.

Can I use pretty JSON for scripting?

Prefer minified JSON for scripts; --pretty is allowed but increases output size and parsing complexity.