asc-testflight-orchestration

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 2b8a88b29324 · 31 Oct 2026Report an issue or request a re-scan

• Publisherrorkai GitHub organizationOwner of the repository this skill is read from
• Source folderrorkai/app-store-connect-cli-skills/skills/asc-testflight-orchestrationThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict2b8a88b29324A new audit runs when the source changes
• Repository statusNot archivedLast push 5 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.

---
name: asc-testflight-orchestration
description: Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.
---

# 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"`
  - A group's builds and testers: `asc testflight groups builds list --group-id "GROUP_ID" --paginate` and `asc testflight groups testers list --group-id "GROUP_ID" --paginate`
- Testers:
  - `asc testflight testers list --app "APP_ID" --paginate`
  - `asc testflight testers add --app "APP_ID" --email "[email protected]" --group "Beta Testers"`
  - `asc testflight testers invite --app "APP_ID" --email "[email protected]"`

## 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`

## Inspect a build's groups
- `asc testflight groups list --build-id "BUILD_ID" --output table`
- The build lookup is experimental. It resolves the app, paginates the app's groups, and includes groups with all-build access.

## Upload without distribution
- `asc publish testflight --app "APP_ID" --ipa "./app.ipa" --upload-only --output json`
- Add `--wait` when the next step needs a processed build.
- Upload-only requires a new IPA or local Xcode build. Do not combine it with an existing `--build-id`, groups, tester notifications, test notes, or beta-review submission. `--build-number` is allowed as upload metadata, but it cannot be the only build input.

## 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.

Excerpt, first 2,348 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/rorkai/app-store-connect-cli-skills
git -C app-store-connect-cli-skills checkout 2b8a88b29324

Works in

1. 2026-10-31
   ✓SAFE B 89 / 100

   first audit · source 2b8a88b29324

Questions about asc-testflight-orchestration

• github.com/rorkai/app-store-connect-cli-skills/tree/main/skills/ — the audited source at commit 2b8a88b29324 and every finding aboveObserved · 31 Oct 2026

Spotted something wrong? Report a correction · Methodology