- name
SKILL.md
File skill tetap berada di repositori penerbit.
Tempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add rorkai/app-store-connect-cli-skills --skill asc-submission-health -a cursor -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add rorkai/app-store-connect-cli-skills --skill asc-submission-health -a claude-code -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add rorkai/app-store-connect-cli-skills --skill asc-submission-health -a codex -yTempel perintah yang disalin di terminal. Perintah itu memasang SKILL.md ini ke agen tersebut.
npx skills add rorkai/app-store-connect-cli-skills --skill asc-submission-health -a grok -yKirim pesan yang disalin di chat Grok Bot. Bot mengambil SKILL.md ini dari GitHub dan menambahkannya ke skill yang dipakai bersama oleh semua Bot Anda.
Install this skill: https://github.com/rorkai/app-store-connect-cli-skills/tree/HEAD/skills/asc-submission-healthDari penerbit
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.
This skill owns:
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.
APP_ID, the version string or VERSION_ID, BUILD_ID, platform, and any known SUBMISSION_ID.asc auth login or ASC_* environment variables.ASC_BYPASS_KEYCHAIN=1 only for repository tests and isolated verification, not normal user sessions.Run the canonical readiness report first:
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:
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:
asc builds info --build-id "BUILD_ID" --output table
# The attached build and submission are in .data.relationships and .included
asc versions view --version-id "VERSION_ID" --include build,appStoreVersionSubmission --output json
For digital goods, run only the relevant product validator:
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.
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.
A version is ready to return to asc-release-flow when:
asc validate has no blocking issues;VALID;asc validate iap and/or asc validate subscriptions checks have no blocking issues, and the required digital-goods versions are prepared;asc-release-flow's multi-item submission reference;Do not call a version ready merely because one validator exits successfully. Report any warning that still needs a web-session or manual check.
Use app-scoped status when the submission ID is unknown:
asc review status --app "APP_ID" --version "1.2.3" --platform IOS --output table
Use exact submission or version IDs when available:
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:
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:
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:
asc review history --app "APP_ID" --version "1.2.3" --paginate --output table
Resolve the exact active submission before cancelling. Preview status first, then require confirmation:
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:
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:
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.
There is no dedicated retry command. Use this sequence:
asc validate and the relevant product validators.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.submit-preflight or submit-create shortcuts.asc-release-flow.--output table for human diagnosis and JSON for automation.--platform MAC_OS while keeping the same health lifecycle.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 fai
---name: asc-submission-healthdescription: Diagnose App Store submission blockers and operate review health with asc, including readiness validation…---# skills/asc-submission-health/SKILL.mdRingkasan umum
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.
FAQ
Unduh skills/asc-submission-health/SKILL.md dari penerbit, atau salin path-nya dan buka repositori. PlugMCP hanya mendaftar skill ini dan tidak meng-host filenya.
Penerbit menyimpannya di https://github.com/rorkai/app-store-connect-cli-skills.
Claude, Cursor, Codex, dan Grok Build bisa membaca SKILL.md yang Anda tambahkan dari repositori penerbit. Grok Bot memasangnya saat Anda mengirim tautan folder GitHub skill tersebut di chat.