Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions.
SkillScore86Maintained
Automatic
◆DevOps & SRE pack
Last verified 10/10/2026
What it changes
Passed 19 of 22 test cases with the skill, and 3 of 22 without it.
Without skill14%
With skill86%
Checks it passed that the model alone missed
Uses --platform MAC_OS in the command arguments.
Hands off submission execution to asc-release-flow.
States overall status first before detailing blockers.
and 14 more in the full report
16 fixed3 passed either way3 still failing0 broke3 errored
Pass-rate lift
+73 pp
Tokens
+23%
Agent turns
0%
Response time
-58%
Model gemini-3.6-flashMeasured 10/10/2026v319 of 25 cases passed with skill · 22 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 16
Prompt
We are running readiness validation for a macOS desktop application release with App ID 11223344 and version 2.0.0. Which platform argument must be passed?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses --platform MAC_OS in the command arguments.
Missed
Passed
case-16 · gemini-3.6-flash · 10/10/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md177 lines4 files
App Store submission health
Use this skill to explain why a release cannot proceed and to manage an existing review submission. Hand healthy release execution back to asc-release-flow.
Ownership boundary
This skill owns:
readiness validation and blocker diagnosis;
public-API, web-session, and manual repair routing;
review status and history;
cancellation and retry decisions.
Use asc-release-flow for staging, upload, publication, and submission. Switching skills continues the current task with its resolved targets, authorization, and verified progress; it does not require the user to restart the workflow. Continue authorized repairs and return to release execution when healthy. Ask for new authority only when a repair exceeds scope.
Answer order
State whether the version is ready, blocked, or already under review.
Name each blocker and the evidence that proves it.
Separate public-API repairs from web-session and manual work.
Run the read-only checks needed to establish the diagnosis. For diagnosis-only requests, report the evidence and one proposed repair command without executing that repair. For authorized execution, continue the repair queue and report completed work and remaining blockers.
Establish the target
Resolve APP_ID, the version string or VERSION_ID, BUILD_ID, platform, and any known SUBMISSION_ID.
Configure auth with asc auth login or ASC_* environment variables.
Use ASC_BYPASS_KEYCHAIN=1 only for repository tests and isolated verification, not normal user sessions.
Prefer IDs once the target is resolved; stop when app, version, or product resolution is ambiguous.