SkillAgentSearch skills...

localization

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 metadata", or "which countries should I target".

Install / Use

npx skills add appeeky/aso-skills --skill localization

Installs into whichever agent you are using.

About this skill
๐Ÿ“„

SKILL.md

Installable skill definition

Quality Score

89/100

Supported Platforms

Universal

Tags

Our assessment of localization

localization scores 89/100 on our quality scale, 500th of 1,155 Content & Media skills we index (top 44%).

Its SKILL.md is 5.9 KB long, well organised into 19 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 2,095 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
17/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so localization is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit โ€” read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk โ€” read a skill before letting an agent act on it.

localization compared with similar skills

All 4 of these similar skills score higher than localization; compare them before choosing.

SkillScoreStarsUpdatedFormat
localization (this skill)by appeeky892.1k3mo agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install localization?
Run npx skills add appeeky/aso-skills --skill localization. The install tabs above show the steps for each supported agent.
Which AI agents does localization work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is localization safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is localization still maintained?
The repository was last updated about 3 months ago, so localization is actively maintained.

name: localization description: 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 metadata", or "which countries should I target". For keyword research in specific markets, see keyword-research. For metadata writing, see metadata-optimization. metadata: version: 1.0.0

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

  1. Check for app-marketing-context.md โ€” read it for current markets and languages
  2. Ask for the App ID (to see current localizations)
  3. Ask: Is the app itself localized (UI, content) or just the store listing?
  4. Ask: Which markets are they considering?
  5. 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:

  1. Run keyword-research for each target market separately
  2. Understand how locals search (different terms, different intent)
  3. Use local autocomplete suggestions
  4. 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)

  1. Analyze top 10 apps in your category in the target market
  2. Run keyword research with local seed terms
  3. Identify local competitors and their positioning
  4. 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

  1. Submit localized metadata
  2. Monitor keyword rankings in each market (weekly)
  3. Track conversion rate by country
  4. 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 market
  • metadata-optimization โ€” Write localized metadata
  • screenshot-optimization โ€” Localize screenshot designs
  • competitor-analysis โ€” Analyze local competitors

Related Skills

View on GitHub
GitHub Stars2.1k
CategoryContent
Updated2mo ago
Forks126

Languages

MDX

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit โ€” see the Safety scan above for what the skill file itself contains.

No cautions
localization โ€” Universal Skill: Install & Safety Check | SkillAgent