asc-id-resolver

Resolve App Store Connect names to IDs for asc CLI workflows.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/pyronaur/ngents --skill asc-id-resolver-pyronaur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-id-resolver
Source: https://github.com/pyronaur/ngents/tree/main/docs/topics/apple/asc-cli/asc-id-resolver
Command: npx skills add https://github.com/pyronaur/ngents --skill asc-id-resolver-pyronaur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve App Store Connect IDs from human-friendly names to simplify CLI automation and scripting.

Core Features & Use Cases

  • Resolve App IDs by bundle-id or name to feed scripts with IDs.
  • Retrieve Build IDs, Version IDs, TestFlight group IDs, and tester IDs for CI workflows.
  • Use in automation to standardize IDs across environments and reduce manual lookups.

Quick Start

Run asc-id-resolver with the app name to obtain APP_ID and set it in your environment for subsequent asc commands.

Frequently Asked Questions about asc-id-resolver

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve App Store Connect IDs from app names for CLI automation?

You can resolve App Store Connect IDs from human-friendly names by using the asc tool to query app data. It maps bundle-ids or app names to their corresponding IDs, outputting the results in JSON format to feed your scripts.

Can I retrieve TestFlight group and tester IDs using the asc command line?

Yes, you can retrieve TestFlight group and tester IDs alongside app, build, and version IDs. The resolver queries App Store Connect data to standardize these lookups for your CI workflows.

What is the best way to automate App Store ID lookups across different environments?

Automating App Store ID lookups is best handled by resolving human-friendly names into JSON outputs. This standardizes IDs across development, testing, and deployment environments, reducing manual lookups in your scripts.

Does the asc-id-resolver output format support JSON for CI pipeline integration?

Yes, the resolver outputs IDs in JSON by default with optional formatting. This supports reliable ID resolution for apps and builds, enabling seamless integration within CI pipelines and automation scripts.

Why do I need to resolve App Store Connect names into IDs before running asc commands?

Resolving names into IDs is required because asc CLI commands rely on specific identifiers rather than human-friendly names. Converting app names or bundle-ids ensures reliable execution for development and deployment workflows.

When do I need to map build and version IDs for App Store Connect testing workflows?

You need to map build and version IDs when automating TestFlight deployments and CI workflows. Resolving these identifiers from human-friendly names ensures reliable lookups across testing and release environments.