Asc Submission Health

This is the checklist you run before hitting submit to the App Store. It walks through the current `asc validate` command, encryption declarations, content rights, metadata verification, screenshot checks, and privacy policy readiness. The skill covers both the safe `asc review submit` flow for prepared versions and the combined upload-and-submit path. It explicitly warns against legacy shortcuts and includes the experimental web-session workarounds for App Privacy publishing and non-renewing IAP attachment, which the public API can't handle. If you've ever had a submission rejected for missing encryption metadata or unpublished privacy details, this gives you the exact sequence to catch it first.

skills.sh installs: 8.3K
GitHub stars: 1.1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add rorkai/app-store-connect-cli-skills --skill asc-submission-health --agent claude-code

Installs into .claude/skills of the current project.

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.