store-listing

Writes and organizes App Store and Google Play listing copy across multiple locales.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/allen-hsu/mobile-shipkit --skill store-listing-allen-hsu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: store-listing
Source: https://github.com/allen-hsu/mobile-shipkit/tree/main/skills/store-listing
Command: npx skills add https://github.com/allen-hsu/mobile-shipkit --skill store-listing-allen-hsu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? App Store and Google Play enforce different length limits, emoji rules, keyword fields, and locale codes, and copy that violates them gets rejected with vague messages. This Skill encodes the exact two-store rules so listing copy passes review on the first submission. ## Core Features & Use Cases - Two-store length and rule tables: Character limits for every field (name 30, short description 80, description 4000, keywords 100), plus ASC's no-emoji rule and keyword deduplication against name/subtitle. - Three-locale localization strategy: zh-Hant as source with en-US and ja as localized rewrites rather than literal translations, including per-market search-term selection. - Canonical directory layout: A metadata/ and play/ JSON structure compatible with asc metadata pull/push and gpc listing push, plus a rejection-fix table for common failures. - Use Case: You need App Store and Play descriptions in zh-Hant, en-US, and ja. The Skill produces emoji-free ASC copy, derives the Play variant, verifies character counts, and lays out files ready to push via asc and gpc. ## Quick Start Write App Store and Google Play listing copy for my app in zh-Hant, en-US, and ja using the store-listing rules and verify all character limits.

Frequently Asked Questions about store-listing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write App Store and Google Play descriptions that pass review?▼

Follow the two-store length table: 30 characters for name/title, 80 for Play short description, and 4000 for full descriptions. Keep the App Store copy completely free of emoji, since ASC rejects the whole batch if any emoji appears in the description.

What are the App Store keyword field rules?▼

App Store keywords are limited to 100 characters separated by ASCII commas, and the commas count toward the limit. Do not repeat words already present in the app name or subtitle, since those are already indexed.

Do full-width Chinese and Japanese characters count as one or two characters in store listings?▼

Full-width ja/zh characters count as 1, not 2, on both stores, which count characters rather than bytes. Verify counts programmatically with python3 len() instead of estimating by eye.

Why was my App Store description rejected with a vague error message?▼

The most common cause is emoji hidden somewhere in the description, which triggers a batch rejection. Search the metadata directory with a Unicode emoji grep pattern and remove every match before resubmitting.

Can I use the same listing copy for App Store and Google Play?▼

No, maintain two copies. The ASC copy is canonical and emoji-free, while the Play copy derives from it and may add emoji and section markers; locale codes also differ (zh-Hant vs zh-TW, ja vs ja-JP).

How should I localize app store copy into English and Japanese?▼

Treat en-US and ja as localized rewrites, not literal translations of the Chinese source. Invent the name per language, use each market's actual search terms for subtitles, and rewrite paragraph content and tone per language.