agentleFS
Sign inStart free
moasqmoasq/ios-dev-agent/.agents/skills/asc-testflight-orchestration/SKILL.md

asc-testflight-orchestration

Skill4 starsChanged 6 months agoMITView on GitHub

Use when distributing TestFlight builds, managing beta groups, adding testers, writing What to Test notes, or checking beta rollout state with asc.

9 other projects use a version of this, 9 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 2 are common, 0 are distinctive, and 1 is very specific to this project.

  • 2

    Common

    Most of the 9 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use this skill when managing TestFlight testers, groups, and build distribution.

    line 8
  2. Very specific:

    Use --paginate on large groups/tester lists.

    line 34
  3. Common:

    Prefer IDs for deterministic operations.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free