Preflight App Store submissions, validate builds, and monitor review status with asc command-line tools.
Works with
Provides pre-submission checklist covering build validation, encryption compliance, content rights declarations, metadata completeness, and localization requirements
Includes two submission workflows: the Review Submissions API (recommended) for granular control, and the simpler asc submit create command for direct version submission
Offers monitoring and cancellation commands to
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionasc-submission-healthExecute the skills CLI command in your project's root directory to begin installation:
Fetches asc-submission-health from rudrankriyam/app-store-connect-cli-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate asc-submission-health. Access via /asc-submission-health in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
708
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
708
stars
Use this skill to reduce review submission failures and monitor status.
asc builds info --build-id "BUILD_ID"
Check:
processingState is VALIDusesNonExemptEncryption - if true, requires encryption declarationIf usesNonExemptEncryption: true:
# If the app should be exempt, patch the local plist helper, rebuild, and re-upload
asc encryption declarations exempt-declare --plist "./Info.plist"
# List existing declarations
asc encryption declarations list --app "APP_ID"
# Create declaration if needed
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
# Assign to build
asc encryption declarations assign-builds \
--id "DECLARATION_ID" \
--build "BUILD_ID"
If the app truly uses only exempt transport encryption, prefer asc encryption declarations exempt-declare --plist "./Info.plist" and rebuild instead of creating a declaration that does not match the binary.
Required for all App Store submissions:
# Check current status
asc apps content-rights view --app "APP_ID"
# Set it for most apps
asc apps content-rights edit --app "APP_ID" --uses-third-party-content=false
Valid values:
DOES_NOT_USE_THIRD_PARTY_CONTENTUSES_THIRD_PARTY_CONTENT# Check version details
asc versions view --version-id "VERSION_ID" --include-build
# Verify copyright is set
asc versions update --version-id "VERSION_ID" --copyright "2026 Your Company"
# List version localizations
asc localizations list --version "VERSION_ID"
# Check required fields: description, keywords, whatsNew, supportUrl
Each locale needs screenshots for the target platform.
# List app info IDs (if multiple exist)
asc apps info list --app "APP_ID"
# Check privacy policy URL
asc localizations list --app "APP_ID" --type app-info --app-info "APP_INFO_ID"
asc can warn about App Privacy readiness, but the public App Store Connect API
cannot verify whether App Privacy is fully published. Before final submission:
asc submit preflight --app "APP_ID" --version "1.2.3" --platform IOS
asc validate --app "APP_ID" --version "1.2.3" --platform IOS
Prefer the version string form for top-level readiness checks in this skill so it stays aligned with asc submit preflight. Lower-level commands later in this guide still use VERSION_ID where the API requires it.
If either command reports an App Privacy advisory, the public API cannot verify publish state. Use the web-session privacy workflow if you rely on those endpoints:
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 "APP_ID" --file "./privacy.json"
asc web privacy publish --app "APP_ID" --confirm
If you do not want to use the experimental asc web privacy ... commands,
confirm App Privacy manually in App Store Connect:
https://appstoreconnect.apple.com/apps/APP_ID/appPrivacy
If the app sells subscriptions or in-app purchases, validate those separately before submit:
asc validate iap --app "APP_ID" --output table
asc validate subscriptions --app "APP_ID" --output table
In current asc, asc validate subscriptions expands MISSING_METADATA into a per-subscription diagnostics matrix. Use it to identify missing review screenshots, promotional images, pricing or availability coverage gaps, offer readiness, and app/build evidence before retrying submit or first-review attach.
Use --output json --pretty when you want exact territory gaps in machine-readable form.
# Create submission
asc review submissions-create --app "APP_ID" --platform IOS
# Add version to submission
asc review items-add \
--submission "SUBMISSION_ID" \
--item-type appStoreVersions \
--item-id "VERSION_ID"
# Submit for review
asc review submissions-submit --id "SUBMISSION_ID" --confirm
asc submit preflight --app "APP_ID" --version "1.2.3" --platform IOS
asc submit create --app "APP_ID" --version "1.2.3" --build "BUILD_ID" --confirm
Use --platform when multiple platforms exist.
# Check submission status
asc submit status --id "SUBMISSION_ID"
asc submit status --version-id "VERSION_ID"
# List all submissions
asc review submissions-list --app "APP_ID" --paginate
# Cancel submission
asc submit cancel --id "SUBMISSION_ID" --confirm
# Or via review API
asc review submissions-cancel --id "SUBMISSION_ID" --confirm
Fix issues, then re-submit.
Check:
The build has usesNonExemptEncryption: true. Either:
ITSAppUsesNonExemptEncryption = NO in Info.plistUse --app-info flag with the correct app info ID:
asc apps info list --app "APP_ID"
asc submit create uses the new reviewSubmissions API automatically.asc submit preflight can return non-blocking advisories; review them before submitting.asc apps content-rights view/edit over ad-hoc app JSON inspection.asc validate subscriptions now provides much richer per-subscription diagnostics for MISSING_METADATA cases.asc web privacy pull|plan|apply|publish is the CLI path for App Privacy.--output table when you want human-readable status.--platform MAC_OS.Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Registry listing for asc-submission-health matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: asc-submission-health is focused, and the summary matches what you get after install.
asc-submission-health is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
asc-submission-health is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in asc-submission-health — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added asc-submission-health from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend asc-submission-health for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
asc-submission-health fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: asc-submission-health is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: asc-submission-health is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 35