Agent skill · marketing growth · dpearson2699

app-store-review

Audits App Store submission readiness and rejection risk across current review guidelines, PrivacyInfo.xcprivacy and required-reason APIs, privacy labels, ATT, StoreKit payments, metadata, entitlements, widgets, and Live Activities. Use when preparing a submission, responding to rejection, reconciling privacy evidence, or separating upload blockers from cleanup.

Why this skill is useful

Provides detailed compliance checks and guidelines specific to App Store submissions that the AI wouldn't reliably generate on its own.

What it needs

About 7k tokens when loaded. Last updated 2026-07-31. 973 stars on the source repository.

What this skill does

App Store Review Preparation Catch App Store rejection risks before submission. Treat policy, SDK, privacy, entitlement, payment, and metadata checks as current release evidence rather than durable facts. Contents Top Rejection Reasons and How to Avoid Them PrivacyInfo.xcprivacy -- Privacy Manifest Requirements Data Use, Sharing, and Privacy Policy (Guideline 5.1.2) In-App Purchase and StoreKit Rules (Guideline 3.1.1) HIG Compliance Checklist App Tracking Transparency (ATT) EU Digital Markets Act (DMA) Considerations Entitlements and Capabilities Submission Workflow Metadata Best Practices Appeal Process Common Mistakes Review Checklist References Start every audit by fetching the current App Review Guidelines, Upcoming Requirements, screenshot specifications, required-reason API documentation, and applicable storefront/entitlement payment rules. Record the checked date and source beside each release blocker. Then archive-build and validate the exact submission, separate blockers from cleanup, fix one class of evidence mismatch, and rerun the same checks against the rebuilt archive. For prompts about keywords, screenshot captions, product-page metadata, or metadata rejection risk, answer from a compliance angle and explicitly defer keyword research, ranking strategy, conversion optimization, screenshot ordering, and A/B testing to app-store-optimization. Keep App Review metadata guidance limited to accuracy, field limits, misleading-content risk, and screenshot compliance. Load the dated format, screenshot, and toolchain facts from Current Release Requirements. For full submission readiness audits, separate blocking upload/review issues from ordinary cleanup. Cross-check privacy manifests, App Store privacy nutrition labels, privacy policy, ATT state, runtime network behavior, and SDK behavior against each other; the declarations and observed behavior must align. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills dpearson2699/app-store-review

View the source on GitHub

Browse the @skills marketplace