Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rorkai/asc-release-flow
Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review.
Passed 20 of 22 test cases with the skill, and 5 of 22 without it.
and 16 more in the full report
15 fixed5 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
During initial setup before running `asc release stage`, a validation check reports that no build is currently attached to version `1.1.0` of app `app_66554`. Should I pause and context-switch to submission health to fix this error?
| Checked | Without skill | With skill |
|---|---|---|
| Continues to the staging step rather than routing an expected unattached build pre-staging result to submission health. | Missed | Passed |
| Explains that staging attaches the build during staging lane execution. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill to carry a release from an approved plan to App Store review. Keep Game Center item preparation here; keep other blocker diagnosis and review recovery in asc-submission-health.
This skill owns:
Use the preparation section for Game Center item preparation or attachment blockers. Use that reference's assembly and submission sections only after the app version is staged and the multi-item lane is selected. Switch to asc-submission-health for other validation blockers, a stuck submission, cancellation, or retry decisions.
Switch skills within the current task, preserving resolved targets, authorization, and verified progress. A failing gate blocks dependent mutations, not diagnosis or independent authorized work. Continue authorized repairs and resume this flow; request new authority only when repairs exceed the agreed scope.
APP_ID, the version string, VERSION_ID when needed, and BUILD_ID when a build already exists.asc auth login or ASC_* environment variables.IOS unless the app targets another platform../metadata when the workflow applies metadata.--confirm for submission.| Intent | Command |
|---|---|
| Prepare metadata and attach an existing build without submitting | asc release stage |
| Submit an already prepared version | asc review submit |
| Upload an IPA or build locally, then optionally submit | asc publish appstore |
| Submit the app version with IAP, subscription, or Game Center version items | lower-level asc review submission commands |
Do not mix lanes after one has already created a review submission. Inspect the existing submission first and continue through the matching lower-level commands.
Apply this gate to a version that already has the intended build attached. For the staging lane, first complete Stage an existing build; asc release stage attaches the build and runs validation, after which this gate can be evaluated. Do not route an expected pre-staging "build not attached" result to asc-submission-health.
test cases passed, vs 5 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.