More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Mobile Store Compliance Auditor

    2

    Catch App Store and Google Play rejection causes before you submit — privacy manifest, permissions, billing, target SDK, ATT

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Mobile Store Compliance Auditor

    Example session with this skill installed

    I'm about to submit my React Native app to the App Store and Google Play. Check it for anything that would get it
    rejected.

    • Read your context and instructions
    • Compiled the mobile store compliance

    Detected: React Native 0.74 (bare). Targeting both App Store and Google Play. I scanned the native config and
    source.

    Writing the full report to MOBILE_STORE_AUDIT.md.

    Summary: 17 findings — 6 Blockers, 5 High, 4 Medium, 2 Low.

    Most urgent: your iOS build will fail upload before review even starts. There's no PrivacyInfo.xcprivacy, but
    React Native and bundled pods call required-reason APIs — App Store Connect rejects this with ITMS-91053. Add the
    privacy manifest declaring each API with an approved reason.

    Other Blockers:

    • Background location requested with no "Always" usage string (iOS rejection).
    • Pro subscription charged via Stripe inside the app — digital goods need StoreKit IAP / Play Billing in most regions.
    • Foreground location service has no foregroundServiceType — crashes on Android 14+.
    • Android targetSdk is 33; Play requires 35 (rising to 36 on Aug 31, 2026).

    Verdict: Not ready — 6 Blockers. Fix the upload-blockers first (privacy manifest, location string, foreground
    type, target SDK), then decide the billing model. Full details with file:line and fixes in MOBILE_STORE_AUDIT.md.

    Store policies shift and reviewers have discretion — verify volatile items (target API, billing) against current docs.

    Writing the full report to MOBILE_STORE_AUDIT.md

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Stop getting rejected. Apple rejects ~25% of submissions and Google blocked 1.75M apps in 2025. This skill audits your app for the concrete reasons reviewers reject, before you hit submit — like a pre-review checklist run by someone who reads the guidelines so you don't have to.

    What it checks

    Apple App Store (16 checks)
    • Privacy Manifest (PrivacyInfo.xcprivacy) + required-reason APIs — the #1 binary rejection of 2024–2026
    • Permission usage strings in Info.plist (missing or generic = rejection)
    • App Tracking Transparency — including the 2025 requirement to name data recipients
    • Account deletion (Guideline 5.1.1(v))
    • In-app purchase vs external payment (Guideline 3.1.1), including the post-Epic US situation
    • Sign in with Apple (Guideline 4.8), encryption compliance, background modes, AI consent disclosure, web-wrapper minimum functionality
    Google Play (15 checks)
    • Target API level (35 now → 36 required Aug 31, 2026)
    • Foreground service types (mandatory Android 14+, crashes without)
    • Restricted permissions — QUERY_ALL_PACKAGES, background location, SMS/Call Log, All Files Access, Contacts (new Oct 2026 policy)
    • Google Play Billing vs alternative billing (US changes Jan 2026, EEA DMA)
    • Data Safety form alignment, account/data deletion, cleartext traffic, AAB + 64-bit, Families policy

    Cross-platform

    Knows where native config lives in React Native, Expo (managed + prebuild), Flutter, Capacitor/Ionic, NativeScript — and the framework-specific traps (the privacy-manifest gap, target-SDK indirection, plugins that add permissions silently)

    How it works

    1. Detects your framework and target stores from project files.
    2. Maps every config surface stores inspect — Info.plist, manifests, entitlements, build.gradle, Expo config, payment code.
    3. Runs the applicable checklists.
    4. Writes MOBILE_STORE_AUDIT.md graded by rejection risk: Blocker / High / Medium / Low. Each finding has the exact file/key location, the guideline cited, what's wrong, and a copy-pasteable fix. A "Verify in store console" section covers what lives outside the repo.

    Why this skill

    • Current as of 2026 — target SDK 35→36, post-Epic billing, ATT recipient disclosure, the 2026 Contacts policy. Most checklists out there are stale.
    • Privacy Manifest focus — the most common modern binary rejection, easy to miss on cross-platform apps.
    • Rejection-risk grading — Blocker means "you literally cannot ship," so you fix the right things first.
    • Honest about volatile rules — for target API level, fees, and external-payment entitlements, it tells the agent to verify against current official docs instead of asserting a stale number.
    • Agent-agnostic — Claude Code, Cursor, Codex CLI, Copilot, Gemini CLI.

    Who it's for

    • Indie devs and teams submitting to the stores for the first time
    • Anyone who's been rejected and wants to know why before resubmitting
    • Cross-platform devs (RN/Flutter/Expo) who keep hitting the privacy-manifest wall
    • Studios shipping apps with ads, subscriptions, location, or AI features

    Limitations

    Static review of code and config only. It does not submit your app, doesn't touch App Store Connect / Play Console, doesn't check store-listing assets (those go in a "Verify in console" section), and doesn't guarantee approval — reviewers exercise discretion. Verify volatile requirements against current official docs.

    Static analysis of code and config only — does not run the app or detect runtime-only issues. Does not submit the app or interact with App Store Connect / Play Console. Does not review store-listing assets (screenshots, descriptions, age-rating answers); those are flagged under "Verify in store console." Does not modify code or config — it only writes the audit report. Does not guarantee approval; reviewers exercise discretion. Volatile requirements (target API level, store fees, external-payment entitlements per country) are snapshotted as of early 2026; the skill instructs verification against current official docs rather than hardcoding values that go stale. Game-engine projects (Unity/Unreal) keep store config in engine player settings; the skill audits exported native config and lists engine-side items for manual verification.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Requires

    cap
    Node.js

    Permissions

    Write Files
    Read Files

    File Scopes

    **/Info.plist
    **/PrivacyInfo.xcprivacy
    **/*.entitlements
    **/AndroidManifest.xml
    **/build.gradle
    **/build.gradle.kts
    **/app.json
    **/app.config.{js
    ts}
    **/capacitor.config.{ts
    json}
    **/pubspec.yaml
    **/package.json
    **/*.{swift
    m
    mm
    kt
    java
    ts
    tsx
    js
    jsx
    dart}
    **/res/xml/**
    MOBILE_STORE_AUDIT.md

    Static analysis only. Reads native config (Info.plist, AndroidManifest.xml, entitlements, build.gradle, Expo/Capacitor config) and source code to detect permission usage, payment flows, tracking SDKs, and account/AI features. Writes a single file (MOBILE_STORE_AUDIT.md) at the repository root. No network calls, no shell commands, no environment reads. If the upload auto-detects "Network Access," it is a false positive — the skill references store API docs in its checklists but never invokes them.

    Listed6 months ago

    What's inside

    Frequently Asked Questions

    The auditor scans your codebase to identify "Blockers" and high-risk issues like missing Privacy Manifests, incorrect target SDK levels, and non-compliant permission strings that lead to immediate rejection. It saves days of back-and-forth by catching technical violations before you hit the submit button.

    This skill is agent-agnostic and works with any AI tool that can access your project files, including Claude Code, Cursor, GitHub Copilot, and the Gemini CLI. It outputs a standardized markdown report that any developer agent can then use to apply fixes.

    Yes, it is specifically designed to handle the "indirection" of cross-platform frameworks. It correctly maps native config files across React Native, Expo (including managed and prebuild), Flutter, and Capacitor, ensuring that plugins don't silently add unannounced permissions.

    The skill is updated quarterly to reflect the latest 2026 store policies, such as the new Android 15/16 target levels and Apple's updated ATT data recipient disclosures. For highly volatile rules like dynamic fee structures, the skill directs the agent to verify against live official documentation.

    The auditor performs a static analysis of your project's configurations, manifests, and entitlements. It does not access your App Store Connect or Google Play Console accounts, nor does it review visual assets like screenshots or app descriptions.

    The skill provides a detailed MOBILE_STORE_AUDIT.md report that categorizes findings by severity. Each issue includes the specific file and key location, the exact store guideline being violated, and copy-pasteable code fixes to resolve the problem.

    New in Security