asc-id-resolver_skill

Overview

This skill resolves App Store Connect entities (apps, builds, versions, beta groups, testers, pre-release versions, and review submissions) from human-friendly names into the numeric IDs required by asc-based commands. It automates the lookup steps so downstream scripts and commands can accept stable IDs instead of brittle name parsing. Use it whenever an asc command requires an ID argument or when you need deterministic references across automation steps.

How this skill works

The skill queries App Store Connect via the asc CLI to list entities and returns the matching ID. It supports looking up apps by bundle ID or app name, selecting latest or recent builds, enumerating versions, listing beta groups and testers, and querying pre-release and review submission records. The skill prefers paginated list commands and deterministic sorting to avoid missed or unstable results and can output JSON or human-friendly tables for debugging.

When to use it

• When an asc command only accepts an entity ID (app, build, version, group, tester, etc.).
• In CI pipelines that need to pin an operation to a specific build or version.
• When resolving the latest build for a given app version and platform.
• Before automating TestFlight operations that require beta-group or tester IDs.
• When gathering pre-release version or review submission IDs for workflows.

Best practices

• Prefer --paginate on listing commands to ensure you retrieve all candidates.
• Use --sort (for example by uploadedDate) to make build selection deterministic.
• Lookup apps by bundle ID when possible to avoid ambiguous names.
• Use --pretty or --output table for human debugging, keep JSON for automation.
• Cache resolved IDs in CI environment variables (e.g., ASC_APP_ID) to avoid repeated lookups.

Example use cases

• Resolve an app ID from a bundle identifier and set ASC_APP_ID for subsequent asc commands.
• Find the latest iOS build ID for version 1.2.3 to submit to TestFlight or release automation.
• List pre-release version IDs to attach release notes or metadata before distribution.
• Lookup a beta group ID to add or remove testers programmatically.
• Fetch review submission IDs to audit or update app review records.