- Home
- Skills
- APIs & Backend
- Google Play Submission Playbook and Listing Checker
Google Play Submission Playbook and Listing Checker
This kit is the order of operations, the files, the checks and the vocabulary that kept a portfolio of two dozen app records straight.
$49
Works with the AI Agents you already use
Google Play Submission Playbook and Listing Checker
Example session with this skill installed
Our Android app got rejected on Google Play for "Misleading Claims" and we have two more apps to submit this month. Get us a repeatable process so this stops happening.
- Read your context and instructions
- Compiled the google play submission
Summary
The rejection was the listing, not the app: it described county court records with no source link and no non-affiliation disclaimer. Fixed the listing, moved all three apps to listing-as-files with the checker in CI, and recorded each submission.
The rejection
node scripts/check-listing.mjs store-listing on the rejected app:
FAIL store-listing
fail: the listing refers to government or public-record information but gives no source URL; Play rejects this as Misleading Claims (missing source link)
fail: the listing refers to government or public-record information but has no clear disclaimer that the app does not represent a government entity
Added the official source URL and "This app is not affiliated with, endorsed by, or representing any government entity." to the full description and the first data screen. Re-check: PASS.
The two new apps
declarations.txt: Price decided (Free), privacy URL public HTTPS, Ads No, target audience adults, IARC category and outcome recorded.data-safety-notes.txtwritten before the questionnaire;reviewer-notes.txtwith numbered steps and no credential (the reviewer account goes only in App access).- Internal testing first, then closed; Production untouched.
Evidence records
node scripts/submission-record.mjs --app ... --track closed --aab release/app.aab --upload-cert release/upload-certificate.pem --console-status "Changes in review" --result "15 changes sent for review" for each app: artifact SHA-256, upload-certificate fingerprint as the console shows it, state in_review. Non-blocking warnings (missing native debug symbols) recorded as warnings.
Vocabulary
The status sheet now uses drafted / submitted / in review / approved / published / available, mapped from the console strings by the script, never guessed upward.
Tests
node --test scripts/playbook.test.mjs: 6 passed.
Connects securely to your tools. The creator never sees your data.
About this skill
Most Play problems are not technical: a paid app that cannot go free and back, a listing that mentions public records without a source link and gets rejected for Misleading Claims, a reviewer password pasted into a notes file, two completed changes nobody pressed submit on, and a status sheet that says approved when the console says in review. This kit is the order of operations, the files, the checks and the vocabulary that kept a portfolio of two dozen app records straight.
Playbook (reference/playbook.md): the vocabulary (drafted, submitted, in review, approved, published, available, rejected, removed, with the console string for each); the decisions that cannot be undone (free or paid, package, upload key custody); the listing as files with the console's limits; the declarations in the order the console asks (privacy URL, App access per role, ads, advertising ID, government, financial, health, Data safety, IARC, target audience, AI assets); tracks and operations (internal, closed, Production untouched, managed publishing, never replace a release in review, a person confirms every submit); the evidence record; the monthly read-only portfolio audit. Rejections (reference/rejections.md): Misleading Claims for government information without source links and the disclaimer that fixes it, policy-source remediation, reviewer sign-in stalls, warnings that are not blockers, completed changes never sent.
Templates: a complete store-listing folder (locale texts, data-safety notes, reviewer notes with numbered steps, declarations).
Scripts: check-listing.mjs fails on limits, missing files, screenshot geometry (reads PNG headers), a password in reviewer notes, a private or non-HTTPS privacy URL, an undecided price, missing Data safety lines, and government wording without source URL and disclaimer; submission-record.mjs writes a record with the artifact SHA-256, the upload certificate fingerprint computed from the PEM as the console shows it, the console strings and the mapped state, and refuses to contain a credential. 6 offline tests. Node 20+, no packages, no network.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Enforces console limits and policy names based on 2026 standards. Does not automate browser interactions or judge visual quality of screenshots. Requires Node 20+.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
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 19 days ago
- Accounts
- Google Play developer account
- Software
Node.js 20+
Also needs the signed AAB and the upload certificate PEM.
Permissions
Shell to run the node scripts and tests; read files for the store-listing folder, the AAB and the certificate PEM; write files for the evidence record JSON. No network access, no environment variables.