agentleFS
Sign inStart free
moasqmoasq/ios-dev-agent/.agents/skills/asc-cli-usage/SKILL.md

asc-cli-usage

Skill4 starsChanged 6 months agoMITView on GitHub

Use when designing, debugging, or running asc CLI commands. Covers flags, output formats, pagination, authentication, JSON parsing, discovery commands, and safe command patterns for App Store Connect workflows.

9 other projects use a version of this, 9 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use asc-apple-ads, asc-in-app-events and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • rudrankriyamSkill

    asc-apple-ads

    Use when managing Apple Ads with asc, including OAuth profiles, ad-account discovery, Platform API v1 campaigns and targeting, reports, assets, recommendations, guarded mutations, raw requests, and Campaign Management API v5 migration.

    Also in 4 projects that use this

  • rorkaiSkill

    asc-in-app-events

    Create and localize App Store in-app events, upload event media, and submit or recover event review submissions with asc. Use when managing in-app events, event card or details page assets, or event-specific submission errors.

    Also in 4 projects that use this

  • eugenepyvovarovSkill

    swift-concurrency-expert

    Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.

    Also in 3 projects that use this

  • kingsidharthSkill

    swiftui-pro

    Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.

    Also in 4 projects that use this

  • jamesrochabrunSkill

    swift-concurrency

    Guide for building, auditing, and refactoring Swift code using modern concurrency patterns (Swift 6+). This skill should be used when working with async/await, Tasks, actors, MainActor, Sendable types, isolation domains, or when migrating legacy callback/Combine code to structured concurrency. Covers Approachable Concurrency settings, isolated parameters, and common pitfalls.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

11 rules. 1 is common, 0 are distinctive, and 10 are very specific to this project.

  • 1

    Common

    Most of the 9 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 10

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when you need to run or design asc commands for App Store Connect.

    line 8
  2. Very specific:

    Always use --help to discover commands and flags.

    line 11
  3. Very specific:

    Prefer view over legacy get aliases for read-only commands in docs and automation.

    line 17
  4. Very specific:

    Prefer edit for update-only availability surfaces and other canonical edit flows.

    line 21
  5. Very specific:

    Keep set where the CLI intentionally models a higher-level replacement/configuration flow and --help still shows set as the canonical verb.

    line 25
  6. Very specific:

    Use explicit long flags (e.g., --app, --output).

    line 28
  7. Common:

    Prefer explicit flags in automation.

    line 29
  8. Very specific:

    Use --paginate when the user wants all pages.

    line 31
  9. Very specific:

    Use --output table or --output markdown only for human-readable output.

    line 35
  10. Very specific:

    Prefer keychain auth via asc auth login.

    line 39
  11. Very specific:

    When permissions are unclear, inspect exact API key role coverage with asc web auth capabilities.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free