rorkai/app-store-connect-cli-skills is a community-maintained collection of Agent Skills for using the asc command-line tool with Apple App Store Connect and Apple Ads. It helps coding agents automate builds, TestFlight, metadata, submissions, signing, and advertising workflows.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add rorkai/app-store-connect-cli-skills --skill asc-testflight-orchestrationgit clone --depth 1 https://github.com/rorkai/app-store-connect-cli-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/rorkai/app-store-connect-cli-skills/asc-testflight-orchestration)<a href="https://agentmods.dev/skills/rorkai/app-store-connect-cli-skills/asc-testflight-orchestration"><img src="https://agentmods.dev/badge/skills/rorkai/app-store-connect-cli-skills/asc-testflight-orchestration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rorkai/app-store-connect-cli-skills/asc-testflight-orchestration"><img src="https://agentmods.dev/badge/skills/rorkai/app-store-connect-cli-skills/asc-testflight-orchestration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.00540 |
| Opus 5 | $0.00016 | $0.00270 |
| Sonnet 5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
asc-testflight-orchestration scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- asc-testflight-orchestration — 100% identical, 0 lines differ
What it actually says
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" --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
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
--waitwhen 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, groups, tester notifications, test notes, or beta-review submission.--build-numberis 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
--paginateon large groups/tester lists. - Prefer IDs for deterministic operations; use the ID resolver skill when needed.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 45 lines · 33 tokens per session scan A 76e23e73ee6c
asc-testflight-orchestration is a skill published in the GitHub repository rorkai/app-store-connect-cli-skills (1,025 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 540 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
app-rejection-recovery
Diagnoses App Store rejections, drafts Resolution Center responses, and plans the fix for resubmission. Use when the user says "my app was rejected", "Apple rejected my app", "App Review rejection", "guideline violation", "Resolution Center response", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "binary…
asc-submission
Prepare an app for App Store submission or TestFlight distribution using the App Store Connect MCP server. Use when user says "prepare submission", "submit to app store", "prepare for review", "update metadata", "set what's new", "check submission readiness", "distribute to testflight", or wants to manage App Store…
asc-build-check
Check the latest CI build status and debug failures using the App Store Connect MCP server. Use when user says "check build", "what broke", "CI status", "build failing", or asks about recent build failures. Also use for signing issues, provisioning profiles, bundle ID capabilities, or Developer Portal queries.
review-management
Pull, cluster, triage, and respond to App Store reviews via the App Store Connect MCP. Use when you need to fetch recent reviews, analyze sentiment, draft developer responses, track recurring themes as product signals, or close the loop on a rating recovery campaign. Trigger phrases: "triage reviews", "respond to…
asc-audit
Read-only drift check between live App Store Connect state, the repo, and whatever launch/submission docs claim. Use before quoting any build/version/TestFlight number back to the user, before trusting a canonical "where we stand" doc block, and as the required first step of submission-preflight before any submit.…
submission-preflight
Pre-submission risk audit for App Store review — catch the rejection triggers (metadata, privacy, IAP, design, account, legal) BEFORE you submit, by app type. Use when the user says "preflight", "will this get rejected", "check before submitting", "review readiness", "submission checklist", "App Review guidelines"…