asc TestFlight Orchestration

VerifiedSafe

Orchestrate TestFlight distribution, groups, testers, and What to Test notes. Use when rolling out betas.

Sby Skills Guide Bot
DevOpsIntermediate
7/28/2026
Claude CodeCursorCodex
#testflight#beta-distribution#app-store-connect#ios#cli

Recommended for

Automated summary

Orchestrates TestFlight distribution — groups, testers, build assignment, and What to Test notes — through the asc CLI commands.

Strengths

  • Covers the whole beta workflow: config export, group creation, tester add/invite, build assignment, and build removal.
  • Provides explicit, copy-pasteable commands, including --paginate for large tester and group lists.
  • Handles What to Test notes per locale and localization-id for multilingual betas.

Limitations

  • Depends entirely on the asc tool and valid APP_ID / BUILD_ID values; no authentication or build upload steps are described.
  • Removing a build from a group requires --confirm, making it a sensitive operation to run carefully.
  • No post-operation verification or rollback procedure is documented.
When to use it

Use it when you need to open a TestFlight beta to a new tester group, redistribute a build, or write its test notes.

When not to use it

Skip it if you need to build, sign, or upload a binary, or manage an App Store submission, since this skill only covers TestFlight configuration.

Security analysis

Safe
Quality score80/100

The skill only documents ordinary `asc` CLI commands for TestFlight configuration, group/tester management, build distribution, and test notes. No shell pipelines, credential access, exfiltration, obfuscated payloads, or destructive filesystem operations are present; the only `--confirm` flag guards a reversible group-removal action.

No concerns found

How this analysis is made

Examples

Set up a beta group
Export the current TestFlight config for app 123456789 to ./testflight.yaml, then create a group called "Beta Testers" and add tester@example.com to it.
Distribute a build with notes
Assign build BUILD_ID to group GROUP_ID using asc, then create What to Test notes in en-US and fr-FR describing the new onboarding flow.
Audit testers
List every TestFlight tester for app 123456789 with --paginate and tell me which ones are not in any group.

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"
  • 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.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/asc-testflight-orchestration-ms47vqmh/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/asc-testflight-orchestration-ms47vqmh' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/asc-testflight-orchestration-ms47vqmh/download' --output '.skill-downloads/asc-testflight-orchestration-ms47vqmh/SKILL.md.part' && mv '.skill-downloads/asc-testflight-orchestration-ms47vqmh/SKILL.md.part' '.skill-downloads/asc-testflight-orchestration-ms47vqmh/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/asc-testflight-orchestration-ms47vqmh/SKILL.md' && test -s '.skill-downloads/asc-testflight-orchestration-ms47vqmh/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/asc-testflight-orchestration' && cp -R '.skill-downloads/asc-testflight-orchestration-ms47vqmh' '.claude/skills/asc-testflight-orchestration'

Cursor
test -f '.skill-downloads/asc-testflight-orchestration-ms47vqmh/SKILL.md' && test -s '.skill-downloads/asc-testflight-orchestration-ms47vqmh/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/asc-testflight-orchestration' && cp -R '.skill-downloads/asc-testflight-orchestration-ms47vqmh' '.cursor/skills/asc-testflight-orchestration'

Codex
test -f '.skill-downloads/asc-testflight-orchestration-ms47vqmh/SKILL.md' && test -s '.skill-downloads/asc-testflight-orchestration-ms47vqmh/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/asc-testflight-orchestration' && cp -R '.skill-downloads/asc-testflight-orchestration-ms47vqmh' '.agents/skills/asc-testflight-orchestration'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/asc-testflight-orchestration-ms47vqmh'

openskills read 'asc-testflight-orchestration-ms47vqmh'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/asc-testflight-orchestration-ms47vqmh/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills