asc-submission-health
Validate App Store submission readiness, submit prepared versions, and monitor review status with current asc commands. Use when shipping or troubleshooting review submissions.
Security Assessment
About asc-submission-health
The asc-submission-health skill helps teams validate App Store submission readiness, reduce review submission failures, and monitor submission health using current App Store Connect CLI workflows. It focuses on the recommended validation process centered around the `asc validate` command and explicitly avoids legacy submission shortcuts. The skill guides users through key preconditions, build verification, compliance checks, metadata validation, and readiness assessments before an app version is submitted for review. By identifying issues earlier in the release process, it helps minimize delays caused by incomplete configuration or submission requirements.
Its capabilities include validating build processing status, running readiness checks in standard or strict modes, reviewing encryption compliance requirements, managing content rights declarations, inspecting version metadata and localizations, validating screenshots, and assessing digital goods readiness for in-app purchases and subscriptions. The skill also provides workflows for metadata repair through pull, validate, and push operations, along with guidance for app information localization and privacy policy configuration. For App Privacy readiness, it documents available advisory and web-session-based validation approaches where public APIs have limitations.
This skill is intended for release engineers, mobile developers, DevOps teams, QA engineers, and anyone responsible for preparing iOS applications for App Store review. It is useful during release preparation, submission troubleshooting, compliance verification, metadata audits, and ongoing monitoring of review readiness. Teams can incorporate it into automated release pipelines or use it manually when diagnosing validation failures before submission.
FAQ
What command should be used to validate App Store submission readiness?
The recommended command is `asc validate`. It can be run against an app and version, or directly against a version ID. A strict mode option is available when warnings should cause automation failures.
What prerequisites should be completed before running validation?
Authentication must be configured, app/version/build identifiers must be resolved, build processing should be complete or handled through a flow that waits for completion, and required metadata, screenshots, review details, encryption information, pricing, and availability should be prepared.
Does this skill help with encryption compliance requirements?
Yes. It includes workflows for reviewing encryption declarations, creating and assigning declarations to builds when needed, and handling exempt transport encryption scenarios through plist-based declarations.
Can the skill validate in-app purchases and subscriptions?
Yes. It includes readiness validation for in-app purchases and subscriptions, with support for structured diagnostics through JSON output when detailed troubleshooting is required.
Are there any limitations related to App Privacy validation?
Yes. The documented workflow notes that the public API cannot fully verify App Privacy publish state. When validation reports an advisory, manual confirmation or the documented web-session-based flow may be required.
Install asc-submission-health
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill