Asc Submission Health
Run App Store Connect readiness checks, submit prepared iOS versions, and monitor review state without deprecated asc shortcuts.
Overview
asc-submission-health is an agent skill for the Ship phase that validates App Store submission readiness, submits prepared versions, and monitors review status using current asc commands.
Install
npx skills add https://github.com/rorkai/app-store-connect-cli-skills --skill asc-submission-healthWhat is this skill?
- Canonical `asc validate` flow with optional `--strict` for CI-style gates
- Pre-submission checklist: build processing state, encryption, metadata, screenshots, review details
- Explicit ban on legacy submit-preflight and submit-create shortcuts
- Supports `--wait` for build processing and version-id based validation
- Encryption compliance queries via `asc encryption declarations list`
- Pre-submission checklist with build status, canonical validate, and encryption compliance sections
Adoption & trust: 676 installs on skills.sh; 845 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are ready to ship an iOS version but unsure whether metadata, builds, encryption, and review prerequisites will pass Apple validation or stall in review.
Who is it for?
Indie iOS developers and small teams automating App Store Connect checks with asc before each review submission.
Skip if: Builders not shipping to the Apple App Store, or teams still expecting legacy asc submit-preflight or submit-create commands.
When should I use this skill?
Shipping or troubleshooting App Store review submissions with asc after auth and IDs are configured.
What do I get? / Deliverables
You get a table-form readiness report from `asc validate`, clear build and encryption checks, and a monitored path to submission without relying on removed asc shortcuts.
- asc validate readiness table output
- Verified VALID build processing and encryption posture
- Submitted version with review status monitoring
Recommended Skills
Journey fit
How it compares
Structured asc CLI checklist for review readiness—not a generic mobile CI pipeline or TestFlight-only upload script.
Common Questions / FAQ
Who is asc-submission-health for?
Solo and indie builders shipping iOS apps who use the App Store Connect CLI and want fewer review rejections from incomplete store assets or build state.
When should I use asc-submission-health?
Use it in Ship when a version is prepared for review, when automation needs strict validation, or when troubleshooting a stuck or failed App Store review submission.
Is asc-submission-health safe to install?
It instructs shell use of asc against your Apple developer account; review the Security Audits panel on this page and treat store credentials and app IDs as sensitive.
SKILL.md
READMESKILL.md - Asc Submission Health
# asc submission health Use this skill to reduce review submission failures and monitor review state. The current readiness command is `asc validate`; legacy submit-preflight and submit-create shortcuts must not be used. ## Preconditions - Auth configured and app/version/build IDs resolved. - Build processing completed or the command uses a high-level flow with `--wait`. - Metadata, app info, screenshots, review details, content rights, encryption, pricing, and availability are expected to be complete. ## Pre-submission checklist ### 1. Verify build status ```bash asc builds info --build-id "BUILD_ID" ``` Check: - `processingState` is `VALID`. - encryption fields are understood before submission. ### 2. Run canonical readiness validation ```bash asc validate --app "APP_ID" --version "1.2.3" --platform IOS --output table ``` Use strict mode when warnings should fail automation: ```bash asc validate --app "APP_ID" --version "1.2.3" --platform IOS --strict --output table ``` If you already have the exact version ID: ```bash asc validate --app "APP_ID" --version-id "VERSION_ID" --platform IOS --output table ``` ### 3. Encryption compliance If the build uses non-exempt encryption: ```bash asc encryption declarations list --app "APP_ID" asc encryption declarations create \ --app "APP_ID" \ --app-description "Uses standard HTTPS/TLS" \ --contains-proprietary-cryptography=false \ --contains-third-party-cryptography=true \ --available-on-french-store=true asc encryption declarations assign-builds \ --id "DECLARATION_ID" \ --build "BUILD_ID" ``` If the app truly uses only exempt transport encryption, prefer updating the local plist and rebuilding: ```bash asc encryption declarations exempt-declare --plist "./Info.plist" ``` ### 4. Content rights declaration ```bash asc apps content-rights view --app "APP_ID" asc apps content-rights edit --app "APP_ID" --uses-third-party-content=false ``` ### 5. Version metadata and localizations ```bash asc versions view --version-id "VERSION_ID" --include-build --include-submission asc localizations list --version "VERSION_ID" --output table ``` For canonical metadata repair: ```bash asc metadata pull --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" asc metadata validate --dir "./metadata" --output table asc metadata push --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" --dry-run --output table asc metadata push --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" ``` ### 6. App info localizations and privacy policy ```bash asc apps info list --app "APP_ID" --output table asc localizations list --app "APP_ID" --type app-info --app-info "APP_INFO_ID" --output table ``` For subscription or IAP apps, make sure privacy policy URL is populated: ```bash asc app-setup info set --app "APP_ID" --primary-locale "en-US" --privacy-policy-url "https://example.com/privacy" ``` ### 7. Screenshots ```bash asc screenshots list --version-localization "LOC_ID" --output table asc screenshots sizes --output table asc screenshots validate --path "./screenshots" --device-type "IPHONE_65" --output table ``` ### 8. Digital goods readiness ```bash asc validate iap --app "APP_ID" --output table asc validate subscriptions --app "APP_ID" --output table ``` Use JSON when you need exact diagnostics: ```bash asc validate subscriptions --app "APP_ID" --output json --pretty ``` ### 9. App Privacy advisory The public API cannot fully verify App Privacy publish state. If validation reports an advisory, use the experimental web-session flow or confirm manually. ```bash asc web privacy pull --app "APP_ID" --out "./privacy.json" asc web privacy plan --app "APP_ID" --file "./privacy.json" asc web privacy apply --app