asc-submission-health

Diagnose App Store submission blockers and manage review status with the asc CLI.

70|4|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/AlexW00/Zettel --skill asc-submission-health-alexw00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-submission-health
Source: https://github.com/AlexW00/Zettel/tree/main/.agents/skills/asc-submission-health
Command: npx skills add https://github.com/AlexW00/Zettel --skill asc-submission-health-alexw00

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? App Store submissions often stall because of hidden readiness blockers such as invalid builds, missing metadata, unresolved encryption declarations, or unprepared in-app purchases. This Skill pinpoints exactly why a release cannot proceed and routes each blocker to the correct repair path. ## Core Features & Use Cases - Readiness Diagnosis: Runs asc validate and asc review doctor to produce an ordered list of blockers with evidence for each one. - Repair Routing: Directs fixes to public-API commands, authenticated web-session commands, or manual App Store Connect steps depending on what the API actually covers. - Review Monitoring and Cancellation: Tracks review status and history, and cancels unhealthy submissions only after confirmation. - Use Case: Your iOS app version is stuck and submission keeps failing. Use this Skill to identify that the build lacks an encryption declaration and the privacy policy URL is missing, fix both, then hand the healthy version back to the release flow. ## Quick Start Ask the assistant to diagnose why my App Store version 1.2.3 cannot be submitted and list the blockers with the next command to run.

Frequently Asked Questions about asc-submission-health

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find out why my App Store submission is blocked?▼

Run asc validate with your app ID, version, and platform to get an ordered readiness report, then run asc review doctor for an explanation of each blocker. The report separates public-API repairs from issues needing web-session or manual fixes.

How do I check App Store review status from the command line?▼

Use asc review status with the app ID and version when the submission ID is unknown, or asc submit status with an exact submission or version ID. The asc review history command distinguishes a current stall from earlier rejected submissions.

Does the App Store Connect API cover App Privacy publishing?▼

No, the public API does not cover the full App Privacy workflow. The asc web privacy commands use an authenticated web session to pull, plan, apply, and publish answers, with manual verification in App Store Connect as a fallback.

When should I cancel an App Store review submission?▼

Cancel only after confirming the exact active submission state with asc submit status and getting user approval, using asc submit cancel with the --confirm flag. Do not cancel solely because review is taking longer than expected.

Can this skill submit a new app version for review?▼

No, submission execution is explicitly out of scope. Once blockers are repaired and validation passes, the healthy version is handed to the asc-release-flow skill, which handles staging, upload, and submission.