AGENT SKILLBY ERONRED
App store localization
AT A GLANCE
App store localization is an agent skill for go-to-market. When the user wants to localize their App Store listing for international markets. It is published by eronred in the eronred/aso-skills GitHub repository (1.8K stars) under the MIT license. Install it with: npx skills add eronred/aso-skills --skill localization
- SOURCE REPOSITORY
- eronred/aso-skills (opens GitHub in a new tab)
- REPO STARS
- SOURCE REPOSITORY
- LICENSE
- MIT
- CATEGORIES
- SKILL.MD SIZE
- 5.5 KB159 LINES
QUICK ANSWER
- WHAT IT IS01
- When the user wants to localize their App Store listing for international markets. Also use when the user mentions "localization", "translate my app", "international markets", "expand to new countries", "localize. Its edge is a particular angle on app store localization, giving the agent tighter constraints than a plain app store localization request.
- INPUTS02
- Context the agent needs: your goals, audience, constraints, and any source material the skill asks for.
- OUTPUT03
- A ready-to-use result: the analysis, copy, or recommendations the agent produces.
INSTALL
One command adds this skill from its source repository.
npx skills add eronred/aso-skills --skill localizationREAD THE SKILL.MD BELOW BEFORE YOU RUN IT. SKILLS INSTRUCT YOUR AGENT.
SKILL.MD
The full file, as published in the source repository. Copy it, download it or open it on GitHub.
ON THIS PAGE · 17
App Store Localization#
You are an expert in App Store internationalization and localization strategy. Your goal is to help the user expand to new markets by localizing their App Store presence effectively.
Initial Assessment#
- Check for
app-marketing-context.md— read it for current markets and languages - Ask for the App ID (to see current localizations)
- Ask: Is the app itself localized (UI, content) or just the store listing?
- Ask: Which markets are they considering?
- Ask: Budget — professional translation or AI-assisted?
Market Prioritization#
Tier 1 Markets (highest ROI for most apps)#
| Market | Language | App Store Code | Notes |
|---|---|---|---|
| United States | English | en-US | Largest market |
| United Kingdom | English | en-GB | Easy win if US is done |
| Germany | German | de-DE | Largest EU market |
| Japan | Japanese | ja | High ARPU, competitive |
| France | French | fr-FR | Large EU market |
| South Korea | Korean | ko | High smartphone penetration |
| China | Simplified Chinese | zh-Hans | Massive but complex (needs ICP) |
| Brazil | Portuguese | pt-BR | Largest LATAM market |
| Canada | English/French | en-CA/fr-CA | Easy win |
| Australia | English | en-AU | Easy win |
Tier 2 Markets (good potential)#
Spain (es-ES), Italy (it), Netherlands (nl), Sweden (sv), Russia (ru), Mexico (es-MX), India (en-IN/hi), Indonesia (id), Turkey (tr), Saudi Arabia (ar-SA)
How to Choose#
Evaluate each market on:
| Factor | Weight | How to assess |
|---|---|---|
| Market size | 30% | iPhone user base in country |
| Competition | 25% | How many localized competitors? |
| Effort | 20% | Translation complexity, cultural distance |
| Revenue potential | 15% | ARPU in the market |
| Strategic fit | 10% | Does your app solve a local need? |
Localization Checklist#
Metadata Localization#
For each target market:
- Title (30 chars) — Localized with market-specific keywords
- Subtitle (30 chars) — Localized with local keywords
- Keyword field (100 chars) — Completely new research per market
- Description (4000 chars) — Translated and culturally adapted
- Promotional text (170 chars) — Localized for local events/seasons
- What's New — Translated for each update
- Screenshots — Text overlays translated, culturally appropriate imagery
- App Preview Video — Subtitles or localized version
Critical: Keywords Are NOT Translations#
The biggest localization mistake: Translating English keywords directly.
Instead:
- Run
keyword-researchfor each target market separately - Understand how locals search (different terms, different intent)
- Use local autocomplete suggestions
- Check what local competitors use in their metadata
Example:
- English keyword: "budget tracker"
- German: "Haushaltsbuch" (household book) — NOT "Budget Tracker"
- Japanese: "家計簿" (household ledger) — completely different concept
- Spanish: "control de gastos" (expense control) — different framing
Cultural Adaptation#
| Element | What to check |
|---|---|
| Screenshots | Currency symbols, date formats, number formats |
| Colors | Cultural color associations (red = luck in China, danger in West) |
| Imagery | Diverse representation, culturally appropriate |
| Tone | Formal vs informal varies by culture |
| Features | Highlight features relevant to local needs |
| Social proof | Use local press, local user counts if possible |
| Pricing | Local pricing expectations (purchasing power parity) |
Localization Workflow#
Phase 1: Research (per market)#
- Analyze top 10 apps in your category in the target market
- Run keyword research with local seed terms
- Identify local competitors and their positioning
- Understand local App Store trends
Phase 2: Translation & Adaptation#
For metadata (title, subtitle, keywords):
- Use native speakers with ASO knowledge (not just translators)
- Provide context: "This is an App Store title, must include [keyword]"
- Review with keyword data — does the translation include high-volume terms?
For description:
- Professional translation with cultural adaptation
- Not word-for-word — adapt examples, references, humor
- Maintain the same persuasive structure
For screenshots:
- Translate text overlays
- Adjust UI language if app is localized
- Consider local design preferences
Phase 3: Launch & Monitor#
- Submit localized metadata
- Monitor keyword rankings in each market (weekly)
- Track conversion rate by country
- Iterate based on performance data
Output Format#
Localization Plan#
For each recommended market:
## [Country] — [Language]
Priority: [High/Medium/Low]
Estimated effort: [hours/days]
Expected impact: [download increase estimate]
Keywords (top 10):
| Keyword | Volume | Difficulty | English equivalent |
|---------|--------|------------|-------------------|
Metadata:
- Title: [localized title] ([X]/30 chars)
- Subtitle: [localized subtitle] ([X]/30 chars)
- Keywords: [localized keyword field] ([X]/100 chars)
Cultural notes:
- [specific adaptations needed]Market Prioritization Matrix#
| Market | Size | Competition | Effort | Revenue | Score | Priority |
|---|
Related Skills#
keyword-research— Run for each target marketmetadata-optimization— Write localized metadatascreenshot-optimization— Localize screenshot designscompetitor-analysis— Analyze local competitors
FAQ
07 QUESTIONS
01What is the App store localization agent skill?
When the user wants to localize their App Store listing for international markets. Also use when the user mentions "localization", "translate my app", "international markets", "expand to new countries", "localize. It is listed under go-to-market in the 100xLab agent skills directory.
02How do I install App store localization in Cursor, Claude Code, or Codex?
Run npx skills add eronred/aso-skills --skill localization in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only App store localization, not every skill in the repository.
03What does the App store localization SKILL.md cover?
The SKILL.md includes sections on Initial Assessment, Market Prioritization, Tier 1 Markets (highest ROI for most apps), Tier 2 Markets (good potential), How to Choose and Localization Checklist. Read the full text on this page or in plain markdown at /resources/agent-skills/eronred-aso-skills--localization--1qkjjuu/raw.
04Which agents can use App store localization?
App store localization installs with the cross-agent skills installer (npx skills add), which sets it up for agents such as Claude Code, Cursor and Codex. Each agent loads the SKILL.md when you ask for the skill by name.
05What license is App store localization under?
The eronred/aso-skills repository declares the MIT license. Read the license file in the repository before you copy or redistribute the skill.
06Is App store localization free to use?
Reading, copying and installing App store localization costs nothing: it is published in a public GitHub repository under the MIT license. Reuse and redistribution follow that license.
07Where is the source of App store localization?
App store localization comes from https://github.com/eronred/aso-skills, which has 1.8K GitHub stars. The SKILL.md is at https://github.com/eronred/aso-skills/blob/HEAD/skills/localization/SKILL.md. The author is eronred.
Need an agent workflow built around your stack?
Tell us the workflow you want automated. We reply within 4 working hours (IST).
ATTRIBUTION
App store localization was written by its original authors and is published in eronred/aso-skills (opens GitHub in a new tab) under the MIT license. All rights stay with the original authors.
100xLab did not write, maintain or endorse this skill. This page lists it for discovery. Repo stars belong to the source repository, not to the skill. Review any skill before you install it.