store-listing
Skill1 starsChanged 51 days agoMITView on GitHub
Create or improve a Google Play and Apple App Store product page — app name, subtitle, short and full description, keywords, promotional text, ASO copy, icon, feature graphic, phone and tablet screenshots at the exact required pixel sizes, preview video, localization, age ratings, Data safety and privacy nutrition labels, and an automated in-engine screenshot pipeline. Use when writing listing text, producing or resizing store graphics, filling Play Console or App Store Connect listing fields, or preparing store assets for a release.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- robertodraGit/skillstheir own version, first seen Nov 8, 2026
- namedtoaster/The-Last-Miletheir own version, first seen Oct 20, 2026
- saif-o99/app-launch-skillstheir own version, first seen Oct 13, 2026
- nvm1410/claude-skillstheir own version, first seen Jun 12, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- namedtoaster/The-Last-Mile★ 39same name
- robertodraGit/skills★ 4same name
- nvm1410/claude-skills★ 0same name
- saif-o99/app-launch-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- app-authSkill
- game-adsSkill
- game-iapSkill
- store-releaseSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Do not guess these; a wrong dimension is rejected at upload.
- Distinctive: line 45
Icon: Must be legible at 48 px. Test it on a real home screen among other icons, not on a white slide.
- Distinctive: line 62
Don't cover the HUD with your caption.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Store Listing
The listing is the only part of your product most people will ever see. Two-thirds of the work is picking the right words for the first 30 characters and the right frames for the first two screenshots; the rest is meeting exact pixel specs so the upload does not bounce.
For signing, building, uploading and getting through review, see the store-release skill.
Exact specs
Do not guess these; a wrong dimension is rejected at upload.
- Google Play —
references/play-listing-specs.md - App Store —
references/app-store-listing-specs.md
Headline numbers, verified 2026-09-24:
| Field | Google Play | App Store |
| App name | 30 chars | 30 chars |
| Subtitle | — | 30 chars |
| Short description | 80 chars | — |
| Promotional text | — | 170 chars (editable without a review) |
| Full description | 4000 chars | 4000 chars |
| Keywords field | — (indexed from name + descriptions) | 100 chars, comma-separated, no spaces after commas |
| Icon | 512×512 PNG, 32-bit with alpha, ≤1024 KB | 1024×1024 PNG, no alpha |
| Feature graphic | 1024×500 JPEG or 24-bit PNG, no alpha | — |
| Screenshots | min 2, 320–3840 px per side | 1–10 per size |
The order to do this in
- Name and subtitle/short description. These carry the keyword weight and are the hardest to
change later (the name is also your brand).
references/aso-copywriting.md - Screenshots. More installs are won or lost here than in the description, which most people never expand. Plan the first two frames as a pair that explains the game without text.
- Icon. Must be legible at 48 px. Test it on a real home screen among other icons, not on a white slide.
- Full description. Written for the human who already tapped; keyword-informed, not keyword-stuffed.
- Feature graphic (Play) and preview video if you have one.
- Declarations: category, age rating, Data safety / privacy labels, target audience.
Screenshots that convert
- Landscape game → landscape screenshots. Play's promotional placements want 16:9 at 1920×1080 minimum, at least four of them, to be eligible for featuring.
- Caption every frame. A short benefit phrase above or below the frame, in the device's language. Screenshots without captions perform worse because the viewer has to decode the UI.
- First two frames must stand alone — they are what appears in search results before anyone swipes.
- Show the actual game. Composited "marketing art" that does not resemble the product is both a conversion trap and, at the extreme, a policy problem on Play ("deceptive store listing").
- Don't cover the HUD with your caption. Frame the screenshot inside a branded canvas and put the caption in the margin instead.
Generating these automatically from the game itself — and keeping them in sync as the UI changes
— is worth the half day it takes: references/screenshot-pipeline.md
Localization
- Localize the name, short description, screenshots and captions first; the full description second. A localized screenshot caption beats a localized paragraph nobody reads.
- Play and Apple both serve the default language when a locale is missing, so a partial localization is safe.
- Machine-translating the listing while the app itself is English-only is a bad trade: the install rises, the rating falls.
- Keyword research is per locale. Translating your English keywords gives you the words nobody searches for in that language.
Declarations that block publishing
| Thing | Where | Note |
| Privacy policy URL | both | must be live, app-specific, and list third parties |
| Data safety | Play Console | must match the app's actual behaviour and your SDKs |
| Privacy nutrition labels | App Store Connect | same, and must agree with Play |
| Content/age rating | both | Play uses the IARC questionnaire; Apple's system now spans 4+/9+/13+/16+/18+ |
| Target audience & content | Play Console | drives the whole Families policy set if children are included |
| Ads declaration | both | if any ad SDK is present, declare it |
| Account deletion URL | Play Console | required if the app has accounts (see app-auth) |
Answer these truthfully the first time. A declaration that contradicts the shipped app is itself the violation, and correcting it later costs a full review cycle.
Checklist before submitting a listing
- Name ≤30 chars and readable when truncated on a phone search result
- Short description/subtitle says what the app is, not what it feels like
- Icon legible at 48 px, no text smaller than the eye can read, no alpha for iOS
- ≥4 phone screenshots at 1080p+, captioned, first two self-explanatory
- Tablet screenshots supplied if the app runs on tablets (Apple requires iPad shots if the app supports iPad; Play surfaces a listing-quality warning without them)
- Feature graphic has no text near the edges (it gets cropped in some placements)
- Every claim in the description is true of the shipped build
- No competitor names, no "#1", no fake urgency — all are policy violations
- Privacy policy URL loads over HTTPS from outside your network
- Data safety / privacy labels regenerated after the last SDK change
Sources
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.