Skip to content
Back to skills

Asc Id Resolver

ASecurity

Use when commands require IDs. Resolve App Store Connect IDs (apps, builds, app and digital-goods versions, groups, testers) from human-friendly names using asc.

  • 7 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 10, 2026
developmentgorailsgitapi

Works with

  • terminal
  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned November 10, 2026

npx -y skills add VelimirMueller/lab-claude-skills --skill asc-id-resolver --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Asc Id Resolver?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Asc Id Resolver
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/velimirmueller-asc-id-resolver/badge)](https://www.skillsdirectory.com/skills/velimirmueller-asc-id-resolver)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: asc-id-resolver
description: Use when commands require IDs. Resolve App Store Connect IDs (apps, builds, app and digital-goods versions, groups, testers) from human-friendly names using asc.
---

# 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 list --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`
- Skip the lookup when attaching or submitting: `asc versions attach-build` and
  `asc review submit` accept `--app`, `--version`, and `--build-number "45"`.

## Version ID
- `asc versions list --app "APP_ID" --paginate`

## Digital-goods version IDs

API 4.4.1 version IDs are distinct from IAP product, subscription, and
subscription-group IDs:

Resolve the owning resources first:

- IAPs: `asc iap list --app "APP_ID" --paginate --output json`
- Subscription groups: `asc subscriptions groups list --app "APP_ID" --paginate --output json`
- Subscriptions: `asc subscriptions list --app "APP_ID" --paginate --output json`
  or `asc subscriptions list --group-id "GROUP_ID" --paginate --output json`

Then resolve their version IDs:

- IAP versions: `asc iap versions list --iap-id "IAP_ID" --paginate --output json`
- Subscription versions: `asc subscriptions versions list --subscription-id "SUB_ID" --paginate --output json`
- Subscription group versions: `asc subscriptions groups versions list --group-id "GROUP_ID" --paginate --output json`

Resolve child localization or image IDs from the corresponding version subtree:

- IAP localizations: `asc iap versions localizations list --version-id "VERSION_ID" --paginate --output json`
- IAP primary image: `asc iap versions image --version-id "VERSION_ID" --output json`
- IAP image collection: `asc iap versions images list --version-id "VERSION_ID" --paginate --output json`
- Subscription localizations: `asc subscriptions versions localizations list --version-id "VERSION_ID" --paginate --output json`
- Subscription primary image: `asc subscriptions versions images primary --version-id "VERSION_ID" --output json`
- Subscription image collection: `asc subscriptions versions images list --version-id "VERSION_ID" --paginate --output json`
- Subscription-group localizations: `asc subscriptions groups versions localizations list --version-id "VERSION_ID" --paginate --output json`

## 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
- Output defaults are TTY-aware: table in a terminal and minified JSON in pipes
  or CI. An explicit `--output` wins.
- Use explicit `--output json` for automation and add `--pretty` only for
  human-readable JSON.
- 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.

Files in this skill

  • LICENSE1 KB
  • SKILL.md3.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in development →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.