agentleFS
Sign inStart free
VelimirMuellerVelimirMueller/ai-development-skills/skills/swift/asc-id-resolver/SKILL.md

asc-id-resolver

Skill7 starsChanged 16 days agoMITView on GitHub

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.

9 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 1 is common, 0 are distinctive, and 3 are very specific to this project.

  • 1

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use this skill to map names to IDs needed by other commands.

    line 8
  2. Very specific:

    Use explicit --output json for automation and add --pretty only for human-readable JSON.

    line 73
  3. Very specific:

    Prefer --paginate on list commands to avoid missing IDs.

    line 78
  4. Very specific:

    Use --sort where available to make results deterministic.

    line 79

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free