asc CLI Usage

VerifiedSafe

Guidance for using asc CLI in this repo (flags, output formats, pagination, auth, and discovery).

Sby Skills Guide Bot
DevelopmentIntermediate
7/22/2026
Claude Code
#app-store-connect#cli#automation#auth#ios

Recommended for

Automated summary

Guides the use of the asc CLI for App Store Connect, covering command discovery, canonical verbs, flags, output formats, authentication, and timeouts.

Strengths

  • Points to --help for discovering current commands and flags.
  • Clarifies canonical view/edit/set verbs and explicit long flags for automation.
  • Covers TTY-aware output, keychain and env-var auth, pagination, and timeout variables.

Limitations

  • Assumes the asc CLI is already installed and App Store Connect API credentials are configured.
  • Focuses on command conventions rather than complete release or metadata workflows.
  • Some verb guidance is version-sensitive and may drift as asc evolves.
When to use it

Use when you need to run, design, or troubleshoot asc commands for App Store Connect.

When not to use it

Do not use when the task does not involve the asc CLI or requires full App Store Connect workflow design beyond command-level guidance.

Security analysis

Safe
Quality score88/100

The skill is documentation-only guidance for using an App Store Connect CLI. It does not instruct destructive actions, network exfiltration, obfuscated payloads, or disabling safety controls. References to authentication environment variables are informational and do not direct users to expose secrets.

No concerns found

How this analysis is made

Examples

Lister les builds en JSON
Utilise asc pour lister tous les builds de l’app APP_ID en JSON, avec pagination.
Configurer l’authentification
Explique comment authentifier asc via le keychain et quelles variables d’environnement utiliser en secours.
Modifier la disponibilité
Conçois une commande asc pour rendre l’app APP_ID disponible dans les territoires USA et GBR.

name: asc-cli-usage description: 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.

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

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.

Timeouts

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

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/asc-cli-usage-mrwakeov/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/asc-cli-usage-mrwakeov' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/asc-cli-usage-mrwakeov/download' --output '.skill-downloads/asc-cli-usage-mrwakeov/SKILL.md.part' && mv '.skill-downloads/asc-cli-usage-mrwakeov/SKILL.md.part' '.skill-downloads/asc-cli-usage-mrwakeov/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/asc-cli-usage-mrwakeov/SKILL.md' && test -s '.skill-downloads/asc-cli-usage-mrwakeov/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/asc-cli-usage' && cp -R '.skill-downloads/asc-cli-usage-mrwakeov' '.claude/skills/asc-cli-usage'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/asc-cli-usage-mrwakeov'

openskills read 'asc-cli-usage-mrwakeov'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/asc-cli-usage-mrwakeov/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills