app-store-submission-blockers-skill

Installation
SKILL.md

App Store Submission Blockers Skill

Purpose

Find the real blocker, prove it from the provider's own records, fix it, and keep the review queue moving. This is a diagnosis-and-unblock skill: it is not store media generation, not ASO copywriting, and not deployment-stack selection.

Never treat an agent summary, a CI badge, or a TestFlight email as proof that a build is in review. Prove the current state first, then act.

Evidence rules (apply before any conclusion)

  • Upload is not submission. A processed build can be App Store eligible for TestFlight while no App Review submission exists.
  • TestFlight is not App Review. "Ready to test" emails say nothing about review state.
  • CI green is not submission. A swallowed API error can leave the pipeline green with nothing submitted.
  • An API 404 is not "the app does not exist". It usually means wrong scope, wrong key, wrong app id, or a purged record.
  • A submission item reading READY_FOR_REVIEW is not proof the parent submission is missing. Read the parent submission, the app version, and the product records.
  • Verdicts and issue notices arrive by email, not through the API. Read the mailbox before concluding that the provider is slow.
  • Timestamps decide the story. Resolve the current submission's submittedDate before describing how long something has "waited".
  • Label every fact: [API-verified], [recorded in a source], [inferred]. Never present a summary as a provider read.
Installs
2
First Seen
Oct 2, 2026