← ClaudeAtlas

play-store-metadatalisted

Author and validate a Google Play listing's text: title, short and full description, release notes per versionCode, and the graphics the listing requires. Use when the user wants the Play listing written, refreshed or checked, says "write the Play listing", "update the Play description", "check the listing limits" ("תכתוב את הליסטינג לפליי"), or when a submission was blocked for a missing feature graphic or an over-limit field. It knows both layouts — a repo's fastlane tree and a studio hub — and validates against Google's limits before anything is sent — so it is the direct route for a single app with no hub, while store-metadata-writer is the one to prefer when a hub holds the profile and both stores have to stay consistent. It does NOT upload (play-store-deliver does), and does NOT build or ship the AAB (play-store-ship).
yybd/app-factory · ★ 5 · Data & Documents · score 77
Install: claude install-skill yybd/app-factory
# Google Play Store Metadata (fastlane supply) > **Conversational language:** talk to the user — questions, summaries, reports — in **the language the user writes in** — unless a `conversational language` is set in the hub `DATA.md` (`$APP_HUB/DATA.md`), which overrides it. This sets the *conversation* language only — content/deliverables follow the app's target locales. Getting a Play listing published means every localized field is present, within Google's character limits, and consistent across languages — and that the things that can't be set programmatically (the Data safety form, the content-rating questionnaire, pricing) get done on the Play Console website. This skill **authors and validates** that metadata; the actual `supply` upload is the **`play-store-deliver`** skill. Guide the user — don't just generate files. Listing copy is a product/marketing decision; ask for the positioning and translate intent faithfully rather than inventing claims. Confirm before installing tools or uploading. > This is the Android counterpart of the **`app-store-metadata`** skill (Apple). > In the **studio flow**, cross-store coordination belongs to > `store-metadata-writer` (Hub): it lifts one copy block from the app's profile > (`$APP_HUB/<slug>/profile.md`), keeps Apple and Play consistent, and > drives this skill for the Play file mechanics — so when a profile exists, take > the copy from there, don't independently re-author or translate it here. > Standalone (no profile): if th