New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

App Store Submission Health

by rorkai in rorkai/app-store-connect-cli-skills

Diagnoses why an App Store version cannot be submitted or is stuck in review, using the asc CLI for validation, repair routing, status checks and retry decisions.

MITAuto-check passedMobile

Install App Store Submission Health

skills CLI
$ npx skills add rorkai/app-store-connect-cli-skills --skill asc-submission-health -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rorkai/app-store-connect-cli-skills asc-submission-health --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rorkai/app-store-connect-cli-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/asc-submission-health .claude/skills/asc-submission-health && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
asc-submission-health
GitHub stars
1.1k
Used in
2 other repos
Token cost
~2.2k tokens
SKILL.md length
968 words
Files
4 (incl. references)
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Diagnoses why an App Store version cannot be submitted or is stuck in review, using the asc CLI for validation, repair routing, status checks and retry decisions.

  • Works in 4 steps: State whether the version is ready,… → Name each blocker and the evidence that… → Separate public-API repairs from… → …
  • App Store validation fails and you need to know why
  • SKILL.md covers Ownership boundary, Answer order, Establish the target and Diagnose readiness, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The skill owns blocker diagnosis and review-health management, and hands staging, upload, publication and submission back to `asc-release-flow` once things are healthy. Answers follow a fixed order: say whether the version is ready, blocked or already under review, name each blocker with the evidence for it, separate repairs possible through the public API from those needing a web session or manual work, and run only read-only checks for a diagnosis. For diagnosis-only requests it reports one proposed repair command without running it.

The agent first resolves the app ID, version, build, platform and any submission ID, with authentication through `asc auth login` or `ASC_*` environment variables, and it stops if the app, version or product is ambiguous. It then runs `asc validate` for the readiness report, `asc review doctor` for an ordered explanation, `asc builds info` and `asc versions view` for evidence, and `asc validate iap` or `asc validate subscriptions` for digital goods, with `--strict` available when warnings should fail automation. Reference files cover app privacy, digital goods and readiness repairs. Cancellation and retry decisions are part of its scope.

When your agent uses it

  • App Store validation fails and you need to know why
  • A version is not in a valid state for submission
  • Review status is unclear or stuck
  • Repairing a failed submission and deciding whether to retry

Example prompts

  • “Validation fails for version 1.2.3 of our iOS app; diagnose the blockers.”
  • “Our review has been waiting for days; show the review status and history.”
  • “App Store Connect says the version is not in a valid state; find out why and what would repair it.”
  • “Cancel the stuck submission and tell me whether it is safe to retry.”

Requirements

  • The `asc` CLI, signed in with `asc auth login` or ASC_* variables
  • An app, version and build in App Store Connect

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. State whether the version is ready, blocked, or already under review.
  2. Name each blocker and the evidence that proves it.
  3. Separate public-API repairs from web-session and manual work.
  4. Run the read-only checks needed to establish the diagnosis. For diagnosis-only requests, report the evidence and one proposed repair…

What it can do on your machine

Read from SKILL.md and the folder at commit 9c7e769. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

App Store Submission Health loads about 2.2k tokens when it runs, and up to ~6.3k if it reads all its reference files. Until then it costs about 108 tokens; SKILL.md has 968 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~108
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rorkai/app-store-connect-cli-skills at commit 9c7e769, republished under its MIT licence (© rorkai). 968 words, ~2,203 tokens.

Download SKILL.mdSave it as .claude/skills/asc-submission-health/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
asc-submission-health
description
Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and retried. For staging, upload, publication, and submission execution, use asc-release-flow.

App Store submission health

Use this skill to explain why a release cannot proceed and to manage an existing review submission. Hand healthy release execution back to asc-release-flow.

Ownership boundary

This skill owns:

  • readiness validation and blocker diagnosis;
  • public-API, web-session, and manual repair routing;
  • review status and history;
  • cancellation and retry decisions.

Use asc-release-flow for staging, upload, publication, and submission. Switching skills continues the current task with its resolved targets, authorization, and verified progress; it does not require the user to restart the workflow. Continue authorized repairs and return to release execution when healthy. Ask for new authority only when a repair exceeds scope.

Answer order

  1. State whether the version is ready, blocked, or already under review.
  2. Name each blocker and the evidence that proves it.
  3. Separate public-API repairs from web-session and manual work.
  4. Run the read-only checks needed to establish the diagnosis. For diagnosis-only requests, report the evidence and one proposed repair command without executing that repair. For authorized execution, continue the repair queue and report completed work and remaining blockers.

Establish the target

  • Resolve APP_ID, the version string or VERSION_ID, BUILD_ID, platform, and any known SUBMISSION_ID.
  • Configure auth with asc auth login or ASC_* environment variables.
  • Use ASC_BYPASS_KEYCHAIN=1 only for repository tests and isolated verification, not normal user sessions.
  • Prefer IDs once the target is resolved; stop when app, version, or product resolution is ambiguous.

Diagnose readiness

Run the canonical readiness report first:

bash
asc validate --app "APP_ID" --version "1.2.3" --platform IOS --output table

Use --version-id "VERSION_ID" when known. Add --strict when warnings must fail automation.

Ask the review-specific doctor for an ordered explanation:

bash
asc review doctor --app "APP_ID" --version "1.2.3" --platform IOS --output table

Collect direct evidence when the report points at the build or version:

bash
asc builds info --build-id "BUILD_ID" --output table
asc versions view --version-id "VERSION_ID" --include-build --include-submission --output table

For digital goods, run only the relevant product validator:

bash
asc validate iap --app "APP_ID" --output table
asc validate subscriptions --app "APP_ID" --output table

Treat the ordered remediation plan from asc validate as the repair queue. Fix and verify one class of blocker before moving to the next.

Route repairs

Use public API commands when the blocker is build processing, metadata, screenshots, review details, encryption, content rights, age rating, availability, or version-scoped product metadata.

Read references/readiness-repairs.md when diagnostics identify one of those common blockers or a first-release availability gap.

Read references/digital-goods.md only when IAP or subscription validation fails, Apple requires first-review attachment, or a versioned product must join an existing review submission.

Read references/app-privacy.md only when validation reports an App Privacy advisory or the publish state cannot be confirmed through the public API.

When validation reports a Game Center component or version blocker, hand it to asc-release-flow and request the multi-item reference's Prepare every item section. Do not route Game Center through general readiness or digital-goods repairs.

Use the web-session commands only for a gap the public API cannot cover, and say that an authenticated Apple web session is required. Keep a manual App Store Connect fallback when the user declines web-session automation.

Decide whether the version is healthy

A version is ready to return to asc-release-flow when:

  • asc validate has no blocking issues;
  • the attached build is VALID;
  • metadata, screenshots, app info, review details, content rights, encryption, age rating, pricing, and availability are resolved;
  • the relevant asc validate iap and/or asc validate subscriptions checks have no blocking issues, and the required digital-goods versions are prepared;
  • any Game Center version items have been checked through asc-release-flow's multi-item submission reference;
  • App Privacy is confirmed or published.

Do not call a version ready merely because one validator exits successfully. Report any warning that still needs a web-session or manual check.

Show full SKILL.md (404 more words)Show less

Monitor review

Use app-scoped status when the submission ID is unknown:

bash
asc review status --app "APP_ID" --version "1.2.3" --platform IOS --output table

Use exact submission or version IDs when available:

bash
asc submit status --id "SUBMISSION_ID" --output table
asc submit status --version-id "VERSION_ID" --output table

Use the release dashboard for surrounding build and review signals:

bash
asc status --app "APP_ID" --include builds,appstore,submission,review --output table

To wait for the review outcome, poll until it settles. The command exits 0 when approved, 1 when rejected, and 7 when still pending at the timeout:

bash
asc status --app "APP_ID" --until review-done --timeout 2h --output json

Status JSON lists suggested follow-ups in summary.nextCommands, each marked with whether it mutates App Store Connect. Treat mutating suggestions as proposals that still need the user's authorization.

Use history to distinguish a current stall from earlier rejected or completed submissions:

bash
asc review history --app "APP_ID" --version "1.2.3" --paginate --output table

Cancel an unhealthy submission

Resolve the exact active submission before cancelling. Preview status first, then require confirmation:

bash
asc submit status --id "SUBMISSION_ID" --output table
asc submit cancel --id "SUBMISSION_ID" --confirm

When resolving by version, include the app for the modern review-submission lookup:

bash
asc submit status --version-id "VERSION_ID" --output table
asc submit cancel --version-id "VERSION_ID" --app "APP_ID" --confirm

The lower-level equivalent is valid when the exact review submission is already known:

bash
asc review submissions-cancel --id "SUBMISSION_ID" --confirm

Do not cancel a submission solely because review is taking longer than expected. Confirm the state and the user's intent first.

Decide when to retry

There is no dedicated retry command. Use this sequence:

  1. Cancel only if the active submission must be withdrawn.
  2. Repair the proven blockers.
  3. Re-run asc validate and the relevant product validators.
  4. Confirm no active submission already owns the version or review items.
  5. Hand the healthy version and any preserved SUBMISSION_ID to asc-release-flow for submission execution. Reuse an inspected READY_FOR_REVIEW draft; create a submission only when no matching draft or active submission exists.

Common failure routing

SymptomFirst evidenceRepair route
Version is not in a valid stateasc validate, asc review doctorordered readiness repairs
Export compliance must be approvedbuild info and encryption declarationreadiness repairs
Multiple app infos foundasc apps info list --app "APP_ID"resolve exact app-info ID
IAP or subscription is not readyproduct validatordigital-goods reference
Game Center component or version is not readyasc validate diagnosticasc-release-flow multi-item preparation section
App Privacy publish state is unclearvalidation advisoryApp Privacy reference
Review appears stuckreview status plus historymonitor; cancel only with evidence and approval

Guardrails

  • Do not use removed submit-preflight or submit-create shortcuts.
  • Do not submit from this skill; return healthy execution to asc-release-flow.
  • Do not treat web-session automation as public App Store Connect API coverage.
  • Do not retry until the earlier submission state and blocker repairs are verified.
  • Use --output table for human diagnosis and JSON for automation.
  • For macOS, use --platform MAC_OS while keeping the same health lifecycle.

© rorkai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/asc-submission-health of rorkai/app-store-connect-cli-skills.

  • SKILL.md
  • references/app-privacy.md
  • references/digital-goods.md
  • references/readiness-repairs.md

Open the folder on GitHubat commit 9c7e769

Used in 2 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in rorkai/app-store-connect-cli-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

App Store Submission Health next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

App Store Submission Health compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
App Store Submission Health this skillrorkai/app-store-connect-cli-skills1.1k2 repos~2.2kAutomated safety check: PassMIT
App Store Preflight Skillstruongduy2611/app-store-preflight-skills1.4k—~1.4kAutomated safety check: PassMIT
OdevioOdevio/Odevio-CLI423—~7.6kAutomated safety check: PassMIT
iOS App Store SubmitZestfulPulse/ios-app-store-submit142—~4.7kAutomated safety check: PassMIT
Expo Deploymentkingstinct/react-native-healthkit7164 repos~930Automated safety check: PassMIT
Mobilevc InstallerJayCRL/MobileVC210—~1.2kAutomated safety check: PassMIT

Similar skills

  • App Store Preflight Skills

    truongduy2611/app-store-preflight-skills

    Scan an iOS/macOS Xcode project for common App Store rejection patterns before submission.

    1.4k GitHub stars~1.4k tokensUpdated 4 mo ago
    MobileAuto-check passed

  • Odevio

    Odevio/Odevio-CLI

    Take a Flutter project to an iPhone or the App Store with Odevio - build, sign and publish iOS apps from Windows, Linux or macOS with no Mac and no Xcode.

    423 GitHub stars~7.6k tokensUpdated 17 days ago
    MobileAuto-check passed

  • iOS App Store Submit

    ZestfulPulse/ios-app-store-submit

    Build, sign, and submit a Flutter/iOS app to the App Store Connect — covers Xcode archive/export, code signing (including headless-Mac keychain workarounds), the asc CLI for App Store Connect…

    142 GitHub stars~4.7k tokensUpdated 10 days ago
    MobileAuto-check passed

  • Expo Deployment

    kingstinct/react-native-healthkit

    Deploying Expo apps to iOS App Store, Android Play Store, web hosting, and API routes

    716 GitHub starsUsed in 4 repos~930 tokens
    MobileAuto-check passed

  • Mobilevc Installer

    JayCRL/MobileVC

    Install and start MobileVC — a Claude Code mobile workspace launcher that lets the user run Claude Code on a phone (iOS / Android) with their dev machine as the backend.

    210 GitHub stars~1.2k tokensUpdated 3 mo ago
    MobileAuto-check passed

  • Expo Dev Client

    kingstinct/react-native-healthkit

    Build and distribute Expo development clients locally or via TestFlight

    716 GitHub starsUsed in 5 repos~879 tokens
    MobileAuto-check passed

More from rorkai/app-store-connect-cli-skills

All 12 skills in this repo

  • App Store Release Flow

    rorkai/app-store-connect-cli-skills

    Orchestrates App Store releases with the asc CLI: staging a version, uploading or building, publishing and submitting for review, with dry-run and confirmation gates.

    1.1k GitHub starsUsed in 2 repos~2k tokens
    Auto-check passed

  • App Store Connect App Creator

    rorkai/app-store-connect-cli-skills

    Creates a new App Store Connect app record by driving the New App form through browser automation, for cases where no public API covers app creation.

    1.1k GitHub starsUsed in 3 repos~1.5k tokens
    Auto-check passed

  • Asc Ppp Pricing

    rorkai/app-store-connect-cli-skills

    Set territory-specific pricing for subscriptions and in-app purchases using current asc setup, pricing summary, price import, and price schedule commands.

    1.1k GitHub starsUsed in 3 repos~4.2k tokens
    Auto-check passed

  • Asc Revenuecat Catalog Sync

    rorkai/app-store-connect-cli-skills

    Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP.

    1.1k GitHub starsUsed in 3 repos~3.8k tokens
    Auto-check passed

  • Asc Subscription Localization

    rorkai/app-store-connect-cli-skills

    Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources.

    1.1k GitHub starsUsed in 2 repos~2.7k tokens
    Auto-check passed

  • Asc Xcode Build

    rorkai/app-store-connect-cli-skills

    Build, archive, generate export options, export, upload, and manage Xcode version/build numbers with the current asc xcode helpers.

    1.1k GitHub starsUsed in 2 repos~2.1k tokens
    Auto-check passed

Works with

Categories

Questions about App Store Submission Health

What does App Store Submission Health do?

Diagnoses why an App Store version cannot be submitted or is stuck in review, using the asc CLI for validation, repair routing, status checks and retry decisions. The skill owns blocker diagnosis and review-health management, and hands staging, upload, publication and submission back to `asc-release-flow` once things are healthy. Answers follow a fixed order: say whether the version is ready, blocked or already under review, name each blocker with the evidence for it, separate repairs possible through the public API from those needing a web session or manual work, and run only read-only checks for a diagnosis.

When should I use App Store Submission Health?

App Store Submission Health fits situations like: app Store validation fails and you need to know why; A version is not in a valid state for submission; review status is unclear or stuck; repairing a failed submission and deciding whether to retry.

How do I install App Store Submission Health in Claude Code?

Run `npx skills add rorkai/app-store-connect-cli-skills --skill asc-submission-health -a claude-code`. Or copy the skill folder (skills/asc-submission-health in rorkai/app-store-connect-cli-skills) into .claude/skills/asc-submission-health in your project. Claude Code loads it when a task matches its description.

How do I install App Store Submission Health in Codex?

Run `npx skills add rorkai/app-store-connect-cli-skills --skill asc-submission-health -a codex`. Or copy the skill folder (skills/asc-submission-health in rorkai/app-store-connect-cli-skills) into .agents/skills/asc-submission-health in your project. Codex loads it when a task matches its description.

Can I use App Store Submission Health in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rorkai/app-store-connect-cli-skills --skill asc-submission-health -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/asc-submission-health, .gemini/skills/asc-submission-health, .github/skills/asc-submission-health and .opencode/skills/asc-submission-health in your project.

What does App Store Submission Health need to run?

SKILL.md names no scripts, command-line tools or credentials: App Store Submission Health is instructions for the agent only. Our summary lists: The `asc` CLI, signed in with `asc auth login` or ASC_* variables; An app, version and build in App Store Connect.

Does App Store Submission Health access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is App Store Submission Health safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does App Store Submission Health use?

App Store Submission Health is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does App Store Submission Health use?

About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.1k tokens, read only when the agent opens those files.

What are the alternatives to App Store Submission Health?

Skills that share tags, products or a category with App Store Submission Health: App Store Preflight Skills (truongduy2611/app-store-preflight-skills, 1.4k stars), Odevio (Odevio/Odevio-CLI, 423 stars), iOS App Store Submit (ZestfulPulse/ios-app-store-submit, 142 stars) and Expo Deployment (kingstinct/react-native-healthkit, 716 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains App Store Submission Health?

rorkai (a GitHub organization) maintains it in rorkai/app-store-connect-cli-skills, which has 1,064 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 5, 2026.

Source: rorkai/app-store-connect-cli-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.