How do I install the Asc CLI Usage skill?

Run npx skillmds@latest add aibot88/asc-cli-usage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Asc CLI Usage safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Asc CLI Usage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Asc CLI Usage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Asc CLI Usage?

aibot88 (@aibot88) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Asc CLI Usage by aibot88 — Agent Skill

Name: Asc CLI Usage
Rating: 4.2 (5 reviews)
Author: aibot88

File contents

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.

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

Frequently asked questions

Asc CLI Usage