Automate this: /mobile-release:preflight runs this audit against the real project, no credentials needed. The App content forms it checks are human-only — see skills/release-automation/references/human-only.md §4 for what an agent can prepare for each instead.

Audit a Google Play listing and its policy declarations before submission. Run every section in order and report PASS, WARN, or FAIL for each. Do not ask which sections to run — run them all. Load only the reference you need for detail.

Confidence marks used throughout this skill and its references: [verified] — read off a primary vendor source on 2026-08-05. [snippet] — secondary source only, plausible but unconfirmed. [unverified] — not confirmed anywhere; run the check given before relying on it.

Audit process:

Read the manifest and Gradle config. Extract applicationId, versionCode, versionName, targetSdk, and every uses-permission. Everything below depends on these.
Walk the pre-submission checklist below, section by section.
Check assets and metadata against references/asset-specs.md. Every number there is unverified — surface that to the user, do not present specs as authoritative.
Check the App content declarations using references/app-content.md.
Check restricted permissions against references/restricted-permissions.md. Propose the narrower API alternative before proposing a declaration form.
Check the launch timeline using references/launch-timeline.md — a new personal developer account cannot reach production quickly.
Preempt rejections using references/rejection-reasons.md.
Produce the summary table in the Output Format below.

play-store-listing