Skip to content
Back to skills

Store Listing

ASecurity

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...

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
developmentgo

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned October 17, 2026

npx -y skills add thomaslimited/game-shipping-skills --skill store-listing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Store Listing?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Store Listing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomaslimited-store-listing/badge)](https://www.skillsdirectory.com/skills/thomaslimited-store-listing)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: store-listing
description: 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.
license: MIT
metadata:
  version: "1.0.0"
  specs-verified: "2026-09-24"
---

# 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

1. **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`
2. **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.
3. **Icon.** Must be legible at 48 px. Test it on a real home screen among other icons, not on a
   white slide.
4. **Full description.** Written for the human who already tapped; keyword-informed, not
   keyword-stuffed.
5. **Feature graphic** (Play) and **preview video** if you have one.
6. **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

- [Play: add preview assets](https://support.google.com/googleplay/android-developer/answer/9866151)
- [App Store Connect screenshot specifications](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications/)
- [Apple age rating updates](https://developer.apple.com/news/?id=ks775ehf)

Files in this skill

  • SKILL.md6.2 KB
  • references/app-store-listing-specs.md4.1 KB
  • references/aso-copywriting.md4 KB
  • references/play-listing-specs.md4.1 KB
  • references/screenshot-pipeline.md4.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.