asc-submission-health
Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and retried. For staging, upload, publication, and submission execution, use asc-release-flow.
npx skills add rorkai/app-store-connect-cli-skills --skill asc-submission-health --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. Do not stage, upload, publish, or submit a healthy release from this skill. ## Answer order 1. State whether the version is ready, blocked, or already under review. 2. Name each blocker and the evidence that proves it. 3. Separate public-API repairs from web-session and manual work. 4. Give one next command. Do not dump the entire repair catalog. ## 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. ## Diagnose readiness Run the canonical r
- Ownership boundary
- Answer order
- Establish the target
- Diagnose readiness
- Route repairs
- Decide whether the version is healthy
- Monitor review
- Cancel an unhealthy submission
- Decide when to retry
- Common failure routing
- Guardrails
asc validate --app "APP_ID" --version "1.2.3" --platform IOS --output table asc review doctor --app "APP_ID" --version "1.2.3" --platform IOS --output table asc builds info --build-id "BUILD_ID" --output table asc versions view --version-id "VERSION_ID" --include-build --include-submission --output table asc validate iap --app "APP_ID" --output table asc validate subscriptions --app "APP_ID" --output table asc review status --app "APP_ID" --version "1.2.3" --platform IOS --output table asc submit status --id "SUBMISSION_ID" --output table asc submit status --version-id "VERSION_ID" --output table asc status --app "APP_ID" --include builds,appstore,submission,review --output table
What does the asc-submission-health skill do?
Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and retried. For staging, upload, publication, and submission execution, use asc-release-flow.
How do I install it?
Run `npx skills add rorkai/app-store-connect-cli-skills --skill asc-submission-health --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rorkai/app-store-connect-cli-skills, a repository with 948 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.