Asc Submission Health
Check App Store Connect submission readiness with asc validate, submit prepared iOS versions, and monitor Apple review status without deprecated CLI 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 with current asc commands.
Install
npx skills add https://github.com/rudrankriyam/asc-skills --skill asc-submission-healthWhat is this skill?
- Canonical readiness command is asc validate—legacy submit-preflight and submit-create must not be used
- Pre-submission flow: build processingState VALID, then validate with optional --strict
- Supports app/version/platform IOS or direct --version-id validation
- Encryption declarations workflow when non-exempt encryption applies
- Designed to reduce review submission failures and track review state
- Three-step pre-submission checklist: build info, asc validate, encryption declarations when required
- Canonical readiness command asc validate replaces legacy submit-preflight and submit-create
Adoption & trust: 1k 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 metadata but keep failing or fear failing App Store review because readiness checks are outdated or incomplete.
Who is it for?
Indie iOS developers using asc in terminal or CI who want a single preflight ritual before Apple review.
Skip if: Android Play Console shipping, teams without asc auth configured, or greenfield apps still missing screenshots and review metadata.
When should I use this skill?
Shipping or troubleshooting App Store review submissions and you need current asc validate-based readiness plus review monitoring.
What do I get? / Deliverables
You run documented asc validate (and related) flows with clear pass/fail signals, handle encryption declarations when needed, and monitor review state after submission.
- Table or structured output from asc validate for a target version
- Verified build processing state and encryption compliance checks
- Review submission and status monitoring command sequence
Recommended Skills
Journey fit
Submission health sits at the boundary of shipping a mobile build to Apple review, after build and metadata work is done. Launch under ship is the canonical shelf because the skill targets review submission, encryption compliance, and post-submit monitoring.
How it compares
Opinionated asc CLI workflow for submission health—not a substitute for Xcode archive quality or full App Store marketing copy skills.
Common Questions / FAQ
Who is asc-submission-health for?
Solo builders and small teams shipping iOS apps with the asc CLI who need repeatable validate-and-monitor steps before and during Apple review.
When should I use asc-submission-health?
Right before submitting a prepared version, when build processing must be VALID, when enabling strict validate in CI, or when debugging a rejected or pending review submission.
Is asc-submission-health safe to install?
Check the Security Audits panel on this Prism page; the skill runs authenticated asc commands against your Apple developer account so treat API keys and app IDs as secrets.
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