Asc Testflight Orchestration
Roll out iOS betas by exporting TestFlight config, managing groups and testers, attaching builds, and publishing What to Test notes with the asc CLI.
Overview
asc-testflight-orchestration is an agent skill for the Ship phase that orchestrates TestFlight groups, testers, build distribution, and What to Test notes using the asc CLI.
Install
npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-testflight-orchestrationWhat is this skill?
- Export TestFlight YAML config with optional builds and testers via asc testflight config export
- Create and paginate groups; add, list, and invite testers by email and group
- Attach or remove builds from groups with deterministic build and group IDs
- Create and update per-locale What to Test notes on builds
- Documents --paginate for large lists and ID-based operations for repeatable runs
Adoption & trust: 2.2k installs on skills.sh; 845 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have uploaded iOS builds but managing TestFlight groups, invites, and tester instructions in the web console is slow and error-prone for repeated beta waves.
Who is it for?
Indie iOS developers shipping frequent TestFlight builds who want scripted beta rollout and consistent What to Test text per locale.
Skip if: Teams not using asc or rudrankriyam’s App Store Connect CLI skills, or builders who only need App Store production submission without TestFlight.
When should I use this skill?
Rolling out TestFlight betas and managing testers, groups, build distribution, or What to Test notes with asc.
What do I get? / Deliverables
Your agent runs documented asc commands so TestFlight config, tester membership, build-to-group mapping, and localized test notes stay reproducible from the terminal.
- Updated TestFlight group and tester state
- Exported testflight.yaml config
- Localized What to Test notes on builds
Recommended Skills
Journey fit
TestFlight is the last mile before public App Store launch—beta distribution, tester access, and release notes belong on the ship shelf under launch prep. Launch subphase covers staged rollout mechanics (who gets which build and what they should verify), which is exactly what this orchestration skill automates.
How it compares
Workflow skill for asc TestFlight commands—not a replacement for Fastlane upload pipelines or manual App Store Connect UI clicks.
Common Questions / FAQ
Who is asc-testflight-orchestration for?
Solo and indie iOS builders who distribute betas through TestFlight and want their coding agent to run asc CLI steps for groups, testers, builds, and release notes.
When should I use asc-testflight-orchestration?
Use it during Ship when rolling out a new beta build, onboarding a tester group, exporting TestFlight YAML for backup or drift review, or updating What to Test instructions before testers install.
Is asc-testflight-orchestration safe to install?
It documents CLI operations that change tester access and build visibility; review the Security Audits panel on this Prism page and confirm destructive flags like --confirm before running in production apps.
SKILL.md
READMESKILL.md - Asc Testflight Orchestration
# asc TestFlight orchestration Use this skill when managing TestFlight testers, groups, and build distribution. ## Export current config - `asc testflight config export --app "APP_ID" --output "./testflight.yaml"` - Include builds/testers: - `asc testflight config export --app "APP_ID" --output "./testflight.yaml" --include-builds --include-testers` ## Manage groups and testers - Groups: - `asc testflight groups list --app "APP_ID" --paginate` - `asc testflight groups create --app "APP_ID" --name "Beta Testers"` - Testers: - `asc testflight testers list --app "APP_ID" --paginate` - `asc testflight testers add --app "APP_ID" --email "tester@example.com" --group "Beta Testers"` - `asc testflight testers invite --app "APP_ID" --email "tester@example.com"` ## Distribute builds - `asc builds add-groups --build-id "BUILD_ID" --group "GROUP_ID"` - Remove from group: - `asc builds remove-groups --build-id "BUILD_ID" --group "GROUP_ID" --confirm` ## What to Test notes - `asc builds test-notes create --build-id "BUILD_ID" --locale "en-US" --whats-new "Test instructions"` - `asc builds test-notes update --localization-id "LOCALIZATION_ID" --whats-new "Updated notes"` ## Notes - Use `--paginate` on large groups/tester lists. - Prefer IDs for deterministic operations; use the ID resolver skill when needed.