asc-testflight-orchestration
Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.
pinned to #0886ecbupdated 3 months ago
Ask your AI client: “install skills/asc-testflight-orchestration”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/asc-testflight-orchestrationmetahub onboarded this repo on the author's behalf.
If you own github.com/rorkai/app-store-connect-cli-skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
899
Last commit
3 months ago
Latest release
published
- #agent-skills
- #ai-skills
- #app-store-connect
- #apple
- #asc
- #automation
- #cicd
- #cli
- #devops
- #ios
- #macos
- #testflight
- #xcode
About this skill
Pulled from SKILL.md at publish time.
Use this skill when managing TestFlight testers, groups, and build distribution.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.0886ecb· 3 months ago
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Kind-specific
3 passed1 warningSkill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: SKILL.md present
found at skills/asc-testflight-orchestration/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
171 words · 1,334 chars · 5 sections
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Release history
1- releasecurrent0886ecbwarn3 months ago
Contents
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" --paginateasc testflight groups create --app "APP_ID" --name "Beta Testers"
- Testers:
asc testflight testers list --app "APP_ID" --paginateasc 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
--paginateon large groups/tester lists. - Prefer IDs for deterministic operations; use the ID resolver skill when needed.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/asc-testflight-orchestration