asc-release-flow Skill for Claude Code: What It Does and How to Install It
Makes Claude stage, upload and submit an App Store release with the asc command line tool, dry run first, then your confirmation.
- Installs
- 8.4K
- on skills.sh
- Stars
- 1.1K
- on GitHub
- Files
- 1
- besides SKILL.md
- Updated
- Oct 2026
- last repo commit
The skill picks one of three release lanes and runs the matching asc command: asc release stage (metadata and build), asc review submit (an already prepared version) or asc publish appstore (upload an IPA or build locally, then optionally submit). It asks for a dry run before any change and --confirm before submission.
It needs the asc CLI installed and signed in with an App Store Connect API key. It bundles no scripts. It hands blockers, stuck submissions and cancellations to a sibling skill, asc-submission-health, so the plugin route is the one to use. This is a community skill pack, not from Apple.
Good for
- iOS and macOS developers who ship through App Store Connect
- Teams that want an agent to run the release steps and stop at a failing check
- Developers shipping an app version together with in-app purchases, subscriptions or Game Center items
Install asc-release-flow
Claude Code
- 1
Copy this prompt.
Install the asc-release-flow skill in Claude Code. Run this command: claude plugin marketplace add rorkai/app-store-connect-cli-skills claude plugin install asc@rorkai Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires asc CLI.
Pick one route. The plugin route installs the asc plugin, which covers the whole repo (26 skill folders in the git tree) and so includes asc-submission-health, the sibling skill this one hands off to. The other routes install only this skill, so also install asc-submission-health. You also need the asc CLI: the asc README gives brew install asc (or curl -fsSL https://asccli.sh/install | bash on macOS and Linux), then asc auth login with an App Store Connect API key. The skill runs the asc CLI, so there is no Claude app tab.
From the project README. Source.
What's in the skill
When it loads
Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review. Use when the user wants to prepare or execute a release. Keep Game Center item preparation in this skill; route other readiness failures, stuck submissions, cancellation, and retry decisions to asc-submission-health.
Sections in SKILL.md
- Ownership boundary
- Preconditions
- Choose the release lane
- Run the readiness gate
- Stage an existing build
- Submit a prepared version
- Upload or build, then publish
- Submit multiple review items
- Handoff after submission
- Guardrails
Key facts
- Installs on skills.sh
- 8,396 (Nov 2, 2026)
- Last repo commit
- Oct 26, 2026
What it includes
Checks a version before any submission; --strict makes warnings stop the run
The readiness gate. Digital goods (IAP, subscriptions) are a hard gate that sends you to asc-submission-health.
Try: “Validate version 1.2.3 of my app before we submit”
Runs code ·
asc validateApplies metadata, attaches a build and validates, without creating a review submission
Run with --dry-run first, then --confirm. A metadata plan with deletes needs --allow-deletes.
Try: “Stage version 2.4.0 with this build and show me the dry-run plan”
Runs code ·
asc release stageSubmits an already prepared version for App Store review
Dry run, then --confirm. Select the build with --build-id or --build-number.
Runs code ·
asc review submitUploads an IPA or builds locally, then optionally submits
Needs --ipa, or --workspace or --project with --scheme. --submit adds the review submission; omit it to upload only.
Runs code ·
asc publish appstoreBuilds one review submission with IAP, subscription or Game Center items
Uses asc review submissions-create and asc review items add after the version is staged. It reuses an existing draft instead of creating a second one.
Runs code ·
Multi-item submissionReports app, version, build and submission IDs, the lane run and the monitor command
Ends with the mutations done under your authorisation. Monitoring, cancellation and retries go to asc-submission-health.
Handoff report
From the official docs
Permissions
High risk
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It can submit an app for review
asc review submit and asc publish appstore --submit send a version to App Store review. The skill requires a dry run and --confirm. Check the plan matches your intended version and build before you agree. github.com
Metadata deletes are possible
If the metadata plan contains deletes, SKILL.md says both runs need --allow-deletes. Read the deletes first. github.com
The plugin installs the whole pack
The Claude plugin covers the repo, which has 26 skill folders including Apple Ads and signing skills. The skills CLI can install this skill alone. github.com
It runs a third-party CLI
asc is an unofficial tool installed by Homebrew or an install script, and not from Apple. The asc README says generate API keys in App Store Connect. github.com
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | The skill uses --dry-run plans before changes, but there is no read-only mode. |
|---|---|
| Talks to | App Store Connect (through the asc CLI) |
| Sign-in and keys | SKILL.md says to configure auth with asc auth login or ASC_* environment variables. The asc README offers --bypass-keychain for config-backed auth where keychain access is not available. |
| Scopes |
|
Questions
What does asc-release-flow do?
It makes Claude carry an App Store release from an approved plan to review with the asc CLI. It chooses between staging, submitting a prepared version, and uploading then publishing, and it checks readiness first.
How do I install it?
Use the install box above. The README documents a Claude Code plugin named asc, which installs the whole pack. You also need the asc CLI itself; the install notes give its commands.
Do I need the asc CLI and an API key?
Yes. SKILL.md says to configure auth with asc auth login or ASC_* environment variables. The asc README says to generate an App Store Connect API key in the Apple developer portal and gives brew install asc as the recommended install.
Does it submit my app without asking?
SKILL.md requires a dry run before a mutating high-level command and --confirm before submission, and says not to add --confirm until the dry-run plan matches the release. Read the plan before you agree.
Why does it mention asc-submission-health?
That is the sibling skill for validation blockers, stuck submissions, cancellation and retry decisions, and for IAP and subscription checks. The plugin route installs it together with this skill.
Is it from Apple?
No. The README says it is a community-maintained, unofficial skill pack and is not affiliated with Apple. The asc CLI is also a third-party tool.
Is it safe?
It runs a CLI that can upload builds, change metadata and submit versions to App Store review under your account. Our advice: use an API key with only the access you need, read each dry-run plan, and keep deletes behind a manual check.
Does it work in the Claude app?
The README documents Claude Code and Codex routes only. The skill runs the asc CLI on your machine, so the install box has no Claude app tab.
Information
updated Nov 2, 2026
- Repository
- rorkai/app-store-connect-cli-skills
- Folder
skills/asc-release-flow
Sources
Docs, issue trackers and discussions this page is built from.
Show all 7Hide
- README.md · github.com
- marketplace.json · github.com
- README.md · github.com
- plugin.json · github.com
- plugin.json · github.com
- SKILL.md · github.com
- multi-item-submissions.md · github.com