agentsclimarketplace
Sign in

Asc testflight orchestration

Skill rorkai/app-store-connect-cli-skills/skills/asc-testflight-orchestration

Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.From its SKILL.md

Install
npx -y skills add rorkai/app-store-connect-cli-skills --skill asc-testflight-orchestration

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • runs commandsInstructs the agent to run 8 commands, including `asc testflight config export --app "APP_ID" --output "./testflight.yaml"` and 7 more.

SKILL.md

1.5 KB, 342 tokens by cl100k_base, as published. Nobody here has run it

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 "[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

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most agent orchestration skills give in 342 tokens

Counted across 848 of the 1,300 authors here whose files we hold, read 2026-09-06

  • Dispatch one agent per independent problem domainin 56 of 848, across 42 files
  • Run full test suite after integrationin 55 of 848, across 42 files
  • Verify fixes do not conflictin 40 of 848, across 32 files
  • Review each summary when agents returnin 40 of 848, across 31 files
  • Write a handoff document summarising the current conversationin 30 of 848, across 25 files
  • Reference existing artifacts by path or URLin 26 of 848, across 24 files
  • Give each agent a specific scopein 19 of 848, across 10 files
  • Give each agent a clear goalin 19 of 848, across 10 files
  • Include a suggested skills section in the documentin 18 of 848, across 16 files
  • Tailor the doc to the user argumentsin 18 of 848, across 15 files
  • Issue all subagent dispatches in the same responsein 17 of 848, across 11 files
  • Use git worktrees for isolationin 17 of 848, across 8 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.