Resolve App Store Connect IDs (apps, builds, versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CamilleScholtz/swmpc --skill asc-id-resolver --agent claude-codeInstalls 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 automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/camillescholtz-asc-id-resolver)More formats (shields.io, HTML) on the badges page.
---
name: asc-id-resolver
description: Resolve App Store Connect IDs (apps, builds, versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.
---
# 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 --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`
## Version ID
- `asc versions list --app "APP_ID" --paginate`
## 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
- JSON is default; use `--pretty` for debug.
- 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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
1. **Strip thinking before verifying** — a verifier that sees the reasoning is biased toward agreement. Fresh context, cleaned proof only. 2. **"Does this prove RH?"** — if your theorem's specialization to ζ is a famous open problem, you have a gap. Most reliable red flag. 3. **Short proof → extract the general lemma** — try 2×2 counterexamples. If general form is false, find what's special about THIS instance. 4. **Same gap twice → step back** — the case split may be obscuring a unifie
Onboard 1-node GitHub MR functional tests for GB200 from existing mr-scoped 2-node tests.
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
Monitor Catchtable for open reservation slots and attempt booking using a logged-in Chrome session.
Interactive walkthrough for new users. Learn by doing — each step creates real content in your vault. Three tracks (researcher, manager, personal) with a universal learning arc. Triggers on "/tutorial", "walk me through", "how do I use this".