Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
Passed 17 of 22 test cases with the skill, and 14 of 22 without it.
and 1 more in the full report
4 fixed13 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to release an iOS update gradually over 7 days to monitor app crash rates before 100% availability. What feature should we configure in App Store Connect?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies Phased Release in App Store Connect as the mechanism for staged 7-day rollouts. | Missed | Passed |
| Explains that phased releases control rollout percentages over a 7-day period. | Passed | Passed |
The instructions your model reads when the skill loads.
Catch App Store rejection risks before submission. Treat policy, SDK, privacy, entitlement, payment, and metadata checks as current release evidence rather than durable facts.
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.
Escalate these as blockers before ordinary cleanup:
| Guideline risk | Release evidence |
test cases passed, vs 14 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.