Asc Submission Health
Run App Store Connect readiness checks and track review status with current `asc validate` flows before you submit an iOS build.
Overview
asc-submission-health is an agent skill for the Launch 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/rudrankriyam/app-store-connect-cli-skills --skill asc-submission-healthWhat is this skill?
- Canonical readiness via `asc validate` (version or version-id) with optional `--strict` for CI
- Pre-submission checklist: build `processingState` VALID, encryption fields, then validate
- Explicitly deprecates legacy submit-preflight and submit-create shortcuts
- Covers encryption declarations, metadata, screenshots, review details, and availability prerequisites
- Troubleshoot stuck or failing review submissions with current asc commands
- 3-step pre-submission checklist (build status, asc validate, encryption compliance)
Adoption & trust: 2.4k installs on skills.sh; 845 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a processed iOS build and filled-in listing data but no reliable, up-to-date checklist to catch review failures before you hit Submit in App Store Connect.
Who is it for?
Indie iOS developers already using the asc CLI who want automation-friendly submission health checks before App Store review.
Skip if: Builders still prototyping features, targeting Android-only stores, or teams without App Store Connect CLI auth and resolved app/version IDs.
When should I use this skill?
Shipping or troubleshooting App Store review submissions with current asc commands.
What do I get? / Deliverables
You get a strict or table-formatted validation pass, encryption compliance verified, and a clearer path to submit and track review without deprecated asc shortcuts.
- Validation report from `asc validate` (table or strict CI pass/fail)
- Confirmed encryption declaration status before submit
- Review submission and status monitoring steps executed via asc
Recommended Skills
Journey fit
Submission validation and review monitoring happen when you are ready to list on the App Store, not during early product coding. ASO covers App Store metadata, builds, review, and store listing compliance—the exact surface this skill automates via asc.
How it compares
Use instead of memorizing deprecated asc submit shortcuts or manual-only checklist scrolling in App Store Connect.
Common Questions / FAQ
Who is asc-submission-health for?
Solo and indie iOS builders shipping with the App Store Connect CLI who need validation and review monitoring without legacy asc commands.
When should I use asc-submission-health?
Use it in Launch (ASO) when a build is processing or VALID and you are submitting or troubleshooting App Store review; also when wiring CI with `asc validate --strict` before release.
Is asc-submission-health safe to install?
Review the Security Audits panel on this Prism page and treat asc credentials and app IDs as secrets; the skill drives CLI calls that touch production App Store Connect data.
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