asc-id-resolver

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

1|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/barronlroth/Cubby --skill asc-id-resolver-barronlroth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-id-resolver
Source: https://github.com/barronlroth/Cubby/tree/main/.agents/skills/asc-id-resolver
Command: npx skills add https://github.com/barronlroth/Cubby --skill asc-id-resolver-barronlroth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mapping human-friendly App Store names to their corresponding App Store Connect IDs (apps, builds, versions, groups, testers), enabling automation workflows that require IDs.

Core Features & Use Cases

  • Resolve IDs from names for apps, builds, versions, groups, and testers.
  • Integrate with scripts and CI pipelines to substitute IDs automatically.
  • Use on-demand to export or reuse IDs in subsequent commands.

Quick Start

Supply a human-friendly app name to receive the corresponding App Store Connect IDs via asc.

Frequently Asked Questions about asc-id-resolver

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

FAQPage Schema
How do I map App Store Connect IDs from app names for automation scripts?

You can query apps, builds, versions, groups, and testers using the asc tooling to return App Store Connect IDs for immediate reuse in automation scripts and CLI workflows where names are easier to reference than IDs.

What is the best way to resolve App Store Connect IDs for CI pipelines?

Supply a human-friendly app name to receive the corresponding App Store Connect IDs, which can be integrated with CI pipelines to substitute IDs automatically within your automation workflows.

Can I resolve IDs for builds, versions, and testers using app names?

Yes, the tool supports resolving IDs from names for apps, builds, versions, groups, and testers, returning the corresponding App Store Connect IDs for immediate reuse in subsequent commands.

Do I need the asc tooling to query App Store Connect IDs from names?

Yes, the tool supports querying apps, builds, versions, groups, and testers through the asc tooling to return App Store Connect IDs for reuse in CLI workflows and automation scripts.

Why does my automation script require App Store Connect IDs instead of app names?

Automation scripts require App Store Connect IDs because underlying API endpoints and CLI workflows expect IDs; this tool resolves the mapping from human-friendly names to the required identifiers for immediate reuse.

When do I need to export App Store Connect IDs for CLI workflows?

You need to export App Store Connect IDs for CLI workflows when subsequent commands require specific identifiers, allowing you to query by name and reuse the returned IDs immediately.