agentleFS
termio-shtermio-sh/termio/skills/asc/SKILL.md

asc

Skill787 starsChanged 3 months agoMITView on GitHub

Drive App Store Connect from the terminal with the `asc` CLI — TestFlight builds, groups, testers and What to Test notes; App Store versions, metadata, keywords, screenshots and release notes; submissions and review health; signing, provisioning and notarization; crash and beta-feedback triage; pricing, subscriptions and Apple Ads. Use whenever the task touches App Store Connect, TestFlight, an App Store release or submission, or an iOS/macOS build upload. Route to the matching file under references/ before running commands.

  • Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every command needs credentials.

    line 16
  2. Very specific:

    If nothing is stored, register a key (Key ID + Issuer ID + .p8 from https://appstoreconnect.apple.com/access/integrations/api):

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 — App Store Connect from the CLI

asc is installed via Homebrew (brew install asc). It is the only tool that should touch App Store Connect here — do not hand-roll JWTs or curl the API.

This skill is a router. Read the one reference that matches the task, not the whole set. Each reference is a self-contained playbook with the exact commands.

Before anything

Every command needs credentials. Check first:

asc auth status      # active profile
asc doctor           # diagnose a broken or missing setup

If nothing is stored, register a key (Key ID + Issuer ID + .p8 from https://appstoreconnect.apple.com/access/integrations/api):

asc auth login --name <label> --key-id <KEY_ID> --issuer-id <UUID> \
  --private-key <path/to/AuthKey_XXXX.p8> --network

Most commands need an app or build ID rather than a name — see references/asc-id-resolver.md.

Routing table

TaskRead
Flags, output formats, pagination, discovery — how to shape any asc commandreferences/asc-cli-usage.md
Turn an app / build / version / group / tester name into an IDreferences/asc-id-resolver.md
TestFlight groups, testers, distribution, What to Test notesreferences/asc-testflight-orchestration.md
Build processing status, finding the latest build, retention cleanupreferences/asc-build-lifecycle.md
TestFlight crashes, beta feedback, hangs, launch diagnosticsreferences/asc-crash-triage.md
Build, archive, export, bump version/build numbers, upload an IPA/PKGreferences/asc-xcode-build.md
Stage a version, publish, submit for reviewreferences/asc-release-flow.md
Validation failures, stuck submissions, cancel and retry decisionsreferences/asc-submission-health.md
Pull, edit, validate and apply App Store metadata and keywordsreferences/asc-metadata-sync.md
Write release notes (What's New) from git log or bulletsreferences/asc-whats-new-writer.md
Translate metadata into more localesreferences/asc-localize-metadata.md
Offline ASO / keyword audit of pulled metadatareferences/asc-aso-audit.md
Capture, frame and upload screenshots (simulator pipeline)references/asc-shots-pipeline.md
Fix screenshot dimensions, alpha channels, validation errorsreferences/asc-screenshot-resize.md
Bundle IDs, capabilities, certificates, provisioning profilesreferences/asc-signing-setup.md
Developer ID signing + notarization for distribution outside the App Storereferences/asc-notarization.md
Territory-specific / PPP pricingreferences/asc-ppp-pricing.md
Subscription and IAP display names across localesreferences/asc-subscription-localization.md
Reconcile the ASC catalog with RevenueCatreferences/asc-revenuecat-catalog-sync.md
Apple Ads campaigns, ad groups, keywords, reportsreferences/asc-apple-ads.md
Repo-local multi-step automations (.asc/workflow.json)references/asc-workflow.md
Create a new app record (browser automation — no public API)references/asc-app-create-ui.md
Submit an entry to the asc Wall of Appsreferences/asc-wall-submit.md

References cross-name each other by their old skill names — a line saying "route to asc-submission-health" means references/asc-submission-health.md in this skill.

Provenance

Vendored from https://github.com/rorkai/app-store-connect-cli-skills at the commit asc install-skills pins (recorded per file in skills-lock.json). Upstream ships these as 23 separate top-level skills; here they are flattened into this one skill's references/, with each skill's own references/ folder nested under references/<skill-name>/ and its links rewritten to match. The prose is otherwise verbatim — do not hand-edit it. To update, run asc install-skills, then re-flatten from ~/.agents/skills/asc-* and delete the global copies.

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.