Asc Id Resolver
Turn App Store Connect app names, bundle IDs, and human labels into the app, build, version, TestFlight, and review submission IDs other asc commands require.
Overview
asc-id-resolver is an agent skill most often used in Ship (also Launch distribution, Operate iterate) that maps App Store Connect names and bundle IDs to asc command IDs.
Install
npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-id-resolverWhat is this skill?
- Resolve APP_ID via `asc apps list` by bundle ID or name; optional `ASC_APP_ID` default
- Latest build lookup with `asc builds info --latest --version --platform IOS`
- Paginated lists for versions, TestFlight groups/testers, pre-release versions, and review submissions
- Output modes: JSON default, `--pretty`, `--output table`, or `--output markdown`
- Guardrail: prefer `--paginate` and `--sort` so ID picks are complete and deterministic
- Covers six ID families: apps, builds, versions, TestFlight groups/testers, pre-release versions, review submissions
Adoption & trust: 2.2k installs on skills.sh; 845 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your asc workflow needs APP_ID, BUILD_ID, or TestFlight IDs but you only know bundle identifiers or display names.
Who is it for?
Indie iOS devs automating TestFlight or App Store steps with rudrankriyam’s asc CLI and multi-app ASC accounts.
Skip if: Android Play Console flows, teams that never use asc, or one-off releases where you already have every UUID in CI secrets.
When should I use this skill?
ASC commands require IDs and you have human-friendly app names, bundle IDs, or version strings instead.
What do I get? / Deliverables
You copy stable IDs into env vars or follow-on asc skills for builds, TestFlight, versions, and review submissions without manual ASC UI hunting.
- Resolved APP_ID, build, version, TestFlight, or review submission identifiers
- Optional ASC_APP_ID default for chained asc commands
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
ID resolution is the gate before TestFlight pushes, version edits, and review submission—canonical shelf is Ship because it unblocks release automation immediately before store submission. Launch subphase covers App Store Connect entities (builds, versions, groups, testers) even when you also use IDs during ongoing release ops.
Where it fits
Resolve APP_ID from bundle ID before uploading a new IPA with asc builds.
List TestFlight group IDs to add external testers without clicking through ASC.
Re-fetch version and review submission IDs after Apple rejects a metadata-only fix.
How it compares
A name-to-ID cookbook for the asc CLI, not a replacement for Apple’s web UI or a standalone ASC MCP server.
Common Questions / FAQ
Who is asc-id-resolver for?
Solo and small-team iOS builders who script App Store Connect with asc and want agents to resolve IDs before running build, TestFlight, or review commands.
When should I use asc-id-resolver?
In Ship before tagging a build or submitting for review, at Launch when wiring TestFlight groups, and in Operate when you re-list versions after Apple metadata changes.
Is asc-id-resolver safe to install?
It only documents read/list asc operations; ASC API keys remain in your environment—check the Security Audits panel on this page before piping credentials into agents.
SKILL.md
READMESKILL.md - Asc Id Resolver
# asc id resolver Use this skill to map names to IDs needed by other commands. ## App ID - By bundle ID or name: - `asc apps list --bundle-id "com.example.app"` - `asc apps list --name "My App"` - Fetch everything: - `asc apps --paginate` - Set default: - `ASC_APP_ID=...` ## Build ID - Latest build: - `asc builds info --app "APP_ID" --latest --version "1.2.3" --platform IOS` - Recent builds: - `asc builds list --app "APP_ID" --sort -uploadedDate --limit 5` ## Version ID - `asc versions list --app "APP_ID" --paginate` ## TestFlight IDs - Groups: - `asc testflight groups list --app "APP_ID" --paginate` - Testers: - `asc testflight testers list --app "APP_ID" --paginate` ## Pre-release version IDs - `asc testflight pre-release list --app "APP_ID" --platform IOS --paginate` ## Review submission IDs - `asc review submissions-list --app "APP_ID" --paginate` ## Output tips - JSON is default; use `--pretty` for debug. - For human viewing, use `--output table` or `--output markdown`. ## Guardrails - Prefer `--paginate` on list commands to avoid missing IDs. - Use `--sort` where available to make results deterministic.