asc-id-resolver

Resolve App Store Connect IDs from human-friendly names for apps, builds, versions, and testers.

4|Updated Dec 8, 2019
One-click install
npx skills add https://github.com/Detrous/dotfiles --skill asc-id-resolver-detrous
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-id-resolver
Source: https://github.com/Detrous/dotfiles/tree/main/claude/skills/asc-id-resolver
Command: npx skills add https://github.com/Detrous/dotfiles --skill asc-id-resolver-detrous

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve App Store Connect IDs (apps, builds, versions, groups, testers) from human-friendly names to enable automated workflows.

Core Features & Use Cases

  • Name-to-ID resolution for apps, builds, versions, and TestFlight elements.
  • Deterministic output with JSON by default; supports pagination and sorting.
  • Use Case: In CI scripts and automation, fetch IDs by name and propagate them to subsequent steps.

Quick Start

Lookup the ASC ID for a given app name and use it in subsequent automation steps.

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 in CI scripts?

App Store Connect ID resolution translates human-friendly app names into unique identifiers to use in subsequent automation steps. It supports CI workflows by outputting predictable JSON, allowing scripts to fetch and propagate IDs automatically.

What is the best way to get TestFlight tester IDs from friendly names?

Getting TestFlight tester IDs from friendly names is done through name-to-ID resolution for TestFlight elements. It looks up human-readable tester names and returns deterministic JSON outputs with matching unique App Store Connect identifiers.

Can I use pagination and sorting to ensure deterministic ID resolution results?

Pagination and sorting are supported to ensure deterministic ID resolution results. By applying these parameters, you get predictable JSON outputs that consistently locate the same App Store Connect IDs across different automation runs.

Does ASC ID resolution work for builds and versions, not just apps?

ASC ID resolution works for builds and versions, not just apps. It performs name-to-ID resolution across apps, builds, versions, groups, and testers, enabling you to locate specific build or version identifiers for your automated workflows.

Why do I need to resolve ASC IDs from human-friendly names for automation?

Resolving ASC IDs from human-friendly names is needed for automation because App Store Connect APIs require specific identifiers rather than names. Translating names to IDs enables automated CI workflows to locate resources and set defaults programmatically.