asc-submission-health
Skill7 starsChanged 20 days agoMITView on GitHub
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. Diagnose App Store submission blockers and operate review health…
9 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- VelimirMueller/claude-skillsword for word, first seen Nov 1, 2026
- The-Artificer-of-Ciphers-LLC/skills-from-the-artificertheir own version, first seen Nov 1, 2026
- deonmenezes/mobile-app-skilledited, first seen Nov 1, 2026
- rorkai/app-store-connect-cli-skillsedited, first seen Oct 26, 2026
- CamilleScholtz/swmpctheir own version, first seen Oct 8, 2026
- malpern/VoxClawtheir own version, first seen Oct 8, 2026
Other versions9 projects use a version of this.
Word for word · 1
- VelimirMueller/claude-skills★ 7100% same
Edited · 3
- rudrankriyam/app-store-connect-cli-skills★ 1.1k98% same
- rorkai/app-store-connect-cli-skills★ 1.1k98% same
- deonmenezes/mobile-app-skill★ 497% same
Wrote their own version · 5
- CamilleScholtz/swmpc★ 239same name
- malpern/VoxClaw★ 208same name
- kumaran-is/claude-code-onboarding★ 35same name
- The-Artificer-of-Ciphers-LLC/skills-from-the-artificer★ 6same name
- moasq/ios-dev-agent★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository156 other files it gives its agents.
- skills/swift/swiftui-design-principles/AGENTS.mdAGENTS.md
- skills/swift/ios-code-audit/CLAUDE.mdCLAUDE.md
- skills/swift/swift-focusengine-pro/llms.txtllms.txt
- build-llm-seamSkill
- build-mcp-serverSkill
- build-rag-pipelineSkill
- secure-llm-featuresSkill
- set-up-llm-evalsSkill
- build-nextjs-backendSkill
- build-supabase-edge-functionSkill
- configure-backend-testsSkill
- design-http-apiSkill
- harden-backendSkill
- scaffold-fastapi-serviceSkill
- scaffold-go-serviceSkill
- scaffold-hono-serviceSkill
- secure-supabase-rlsSkill
- set-up-backend-authSkill
- set-up-background-jobsSkill
- set-up-databaseSkill
- set-up-nextjs-supabase-authSkill
- set-up-observabilitySkill
- set-up-supabaseSkill
- build-cliSkill
- release-cliSkill
- set-up-dev-toolchainSkill
- audit-securitySkill
- audit-toolchainSkill
- extend-skillsetSkill
- promote-releaseSkill
- set-up-stack-profileSkill
- write-commit-messagesSkill
- write-pull-requestsSkill
- analyze-complexitySkill
- apply-algorithmsSkill
- apply-design-patternsSkill
- apply-design-principlesSkill
- apply-solidSkill
- choose-data-structureSkill
- debug-systematicallySkill
- enforce-dependency-ruleSkill
- refactor-safelySkill
- slice-and-estimateSkill
- write-clean-testsSkill
- write-readable-codeSkill
- clean-frontend-scaffoldingSkill
- configure-accessibilitySkill
- configure-analyticsSkill
- configure-ciSkill
- configure-error-trackingSkill
- configure-lintingSkill
- configure-test-stackSkill
- configure-typescriptSkill
- create-moduleSkill
- optimize-performanceSkill
- scaffold-frontend-projectSkill
- set-up-authSkill
- set-up-design-systemSkill
- set-up-document-headSkill
- set-up-error-boundariesSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
26 rules. 0 are common, 18 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
18
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill to explain why a release cannot proceed and to manage an existing review submission.
- Distinctive: line 26
Run the read-only checks needed to establish the diagnosis.
- Very specific: line 32
Use ASC_BYPASS_KEYCHAIN=1 only for repository tests and isolated verification, not normal user sessions.
- Distinctive: line 33
Prefer IDs once the target is resolved.
- Distinctive: line 37
Run the canonical readiness report first:
- Very specific: line 43
Use --version-id "VERSION_ID" when known.
- Distinctive: line 45
Ask the review-specific doctor for an ordered explanation:
- Very specific: line 66
Treat the ordered remediation plan from asc validate as the repair queue.
- Distinctive: line 70
Use public API commands when the blocker is build processing, metadata, screenshots, review details, encryption, content rights, age …
- Distinctive: line 72
Read references/readiness-repairs.md when diagnostics identify one of those common blockers or a first-release availability gap.
- Distinctive: line 74
Read references/digital-goods.md only when IAP or subscription validation fails, Apple requires first-review attachment, or a versioned …
- Distinctive: line 76
Read references/app-privacy.md only when validation reports an App Privacy advisory or the publish state cannot be confirmed through the …
- Very specific: line 78
When validation reports a Game Center component or version blocker, hand it to asc-release-flow and request the multi-item reference's …
- Distinctive: line 80
Use the web-session commands only for a gap the public API cannot cover, and say that an authenticated Apple web session is required.
- Distinctive: line 93
Do not call a version ready merely because one validator exits successfully.
- Distinctive: line 97
Use app-scoped status when the submission ID is unknown:
- Distinctive: line 103
Use exact submission or version IDs when available:
- Distinctive: line 110
Use the release dashboard for surrounding build and review signals:
- Distinctive: line 124
Use history to distinguish a current stall from earlier rejected or completed submissions:
- Distinctive: line 139
When resolving by version, include the app for the modern review-submission lookup:
- Distinctive: line 152
Do not cancel a submission solely because review is taking longer than expected.
- Very specific: line 178
Do not use removed submit-preflight or submit-create shortcuts.
- Very specific: line 179
Do not submit from this skill.
- Distinctive: line 180
Do not treat web-session automation as public App Store Connect API coverage.
- Distinctive: line 181
Do not retry until the earlier submission state and blocker repairs are verified.
- Very specific: line 182
Use --output table for human diagnosis and JSON for automation.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- State whether the version is ready, blocked, or already under review.
- Name each blocker and the evidence that proves it.
- Separate public-API repairs from web-session and manual work.
- 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 orVERSION_ID,BUILD_ID, platform, and any knownSUBMISSION_ID. - Configure auth with
asc auth loginorASC_*environment variables. - Use
ASC_BYPASS_KEYCHAIN=1only 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:
asc validate --app "APP_ID" --version "1.2.3" --platform IOS --output tableUse --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 tableCollect 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 jsonFor digital goods, run only the relevant product validator:
asc validate iap --app "APP_ID" --output table
asc validate subscriptions --app "APP_ID" --output tableTreat 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 validatehas 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 iapand/orasc validate subscriptionschecks 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.
Monitor review
Use app-scoped status when the submission ID is unknown:
asc review status --app "APP_ID" --version "1.2.3" --platform IOS --output tableUse exact submission or version IDs when available:
asc submit status --id "SUBMISSION_ID" --output table
asc submit status --version-id "VERSION_ID" --output tableUse the release dashboard for surrounding build and review signals:
asc status --app "APP_ID" --include builds,appstore,submission,review --output tableTo 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 jsonStatus 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 tableCancel an unhealthy submission
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" --confirmWhen 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" --confirmThe lower-level equivalent is valid when the exact review submission is already known:
asc review submissions-cancel --id "SUBMISSION_ID" --confirmDo 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:
- Cancel only if the active submission must be withdrawn.
- Repair the proven blockers.
- Re-run
asc validateand the relevant product validators. - Confirm no active submission already owns the version or review items.
- Hand the healthy version and any preserved
SUBMISSION_IDtoasc-release-flowfor submission execution. Reuse an inspectedREADY_FOR_REVIEWdraft; create a submission only when no matching draft or active submission exists.
Common failure routing
| Symptom | First evidence | Repair route |
| Version is not in a valid state | asc validate, asc review doctor | ordered readiness repairs |
| Export compliance must be approved | build info and encryption declaration | readiness repairs |
| Multiple app infos found | asc apps info list --app "APP_ID" | resolve exact app-info ID |
| IAP or subscription is not ready | product validator | digital-goods reference |
| Game Center component or version is not ready | asc validate diagnostic | asc-release-flow multi-item preparation section |
| App Privacy publish state is unclear | validation advisory | App Privacy reference |
| Review appears stuck | review status plus history | monitor; cancel only with evidence and approval |
Guardrails
- Do not use removed
submit-preflightorsubmit-createshortcuts. - 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 tablefor human diagnosis and JSON for automation. - For macOS, use
--platform MAC_OSwhile keeping the same health lifecycle.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

