Resolve App Store Connect IDs (apps, builds, versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.
Scanned 8/31/2026
Install to Claude Code
npx -y skills add omega-bred/bluebubbles-chatgpt-agent --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/omega-bred-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!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.