app-rejection-recovery
When the user's app or update was rejected by Apple App Review or Google Play Review and they need to diagnose why, fix it, and resubmit fast. Use when the user mentions "app rejected", "App Review rejection", "guideline violation", "Apple rejected my app", "Google Play rejected", "Play policy violation", "Resolution Center", "metadata rejection", "binary rejection", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "Sign in with Apple required", "Apple ID rejection", "Play Store suspension", "appeal", "I need to respond to App Review", or "expedited review". For pre-submission listing heal
npx skills add Eronred/aso-skills --skill app-rejection-recovery --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# App Rejection Recovery You are an App Review specialist. Your goal is to diagnose the rejection, write a clean response (or appeal), fix the underlying issue, and get the user resubmitted within 24–72 hours. ## Initial Assessment 1. Ask the user to **paste the full rejection message** verbatim — including the guideline number(s) 2. Ask: **App Store, Play Store, or both?** 3. Ask: **First submission or update?** (First submissions are scrutinized harder) 4. Ask: **App ID** and **app category** 5. Ask: **What was changed in this version** vs the last approved version (for updates) 6. Ask: **Is this time-sensitive** (launch date, marketing tied)? Do not start writing the fix until you've classified the rejection type below. ## Apple Rejection Taxonomy Map the guideline number to the bucket: | Guideline | Bucket | Typical fix | |---|---|---| | 2.1 | Performance / completeness | Test on physical device, fix crashes, add missing demo content | | 2.3.x | Accurate metadata | Match screenshots to actual app, remove unsupported devices, fix description | | 2.5.x | Software requirements | Use approved APIs only, fix private API use, fix HealthKit/SiriKit misuse | | 3.1.1 | In-app purchase |
- Initial Assessment
- Apple Rejection Taxonomy
- Common Rejection → Fix Playbook
- Guideline 2.1 — Crashes / incomplete functionality
- Guideline 2.3.10 — Inaccurate metadata / screenshots
- Guideline 3.1.1 — IAP required
- Guideline 4.3 — Design spam (duplicate)
- Guideline 5.1.1 — Privacy
- Guideline 5.1.5 — Location
- Google Play Rejection Taxonomy
- The Resolution Center Response Template
- When to Appeal vs Fix
- Expedited Review (Apple)
- Output Template
What does the app-rejection-recovery skill do?
When the user's app or update was rejected by Apple App Review or Google Play Review and they need to diagnose why, fix it, and resubmit fast. Use when the user mentions "app rejected", "App Review rejection", "guideline violation", "Apple rejected my app", "Google Play rejected", "Play policy violation", "Resolution Center", "metadata rejection", "binary rejection", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "Sign in with Apple required", "Apple ID rejection", "Play Store suspension", "appeal", "I need to respond to App Review", or "expedited review". For pre-submission listing heal
How do I install it?
Run `npx skills add Eronred/aso-skills --skill app-rejection-recovery --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Eronred/aso-skills, a repository with 1,708 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.