Asc Metadata Sync
n0an/VivaDicta
Sync and validate App Store metadata and localizations with asc, including legacy metadata format migration.
When the user wants to localize their App Store listing for international markets.
Install Localization
$ npx skills add appeeky/aso-skills --skill localization -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install appeeky/aso-skills localization --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/localization .claude/skills/localization && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "localization" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/localization into .claude/skills/localization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "localization", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/appeeky/aso-skills/tree/main/skills/localizationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add appeeky/aso-skills --skill localization -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install appeeky/aso-skills localization --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/localization .agents/skills/localization && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "localization" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/localization into .agents/skills/localization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "localization", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add appeeky/aso-skills --skill localization -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install appeeky/aso-skills localization --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/localization .cursor/skills/localization && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "localization" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/localization into .cursor/skills/localization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "localization", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/appeeky/aso-skills.git --path skills/localization--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add appeeky/aso-skills --skill localization -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install appeeky/aso-skills localization --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/localization .gemini/skills/localization && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "localization" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/localization into .gemini/skills/localization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "localization", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install appeeky/aso-skills localizationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add appeeky/aso-skills --skill localization -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/localization .github/skills/localization && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "localization" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/localization into .github/skills/localization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "localization", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add appeeky/aso-skills --skill localization -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install appeeky/aso-skills localization --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/localization .opencode/skills/localization && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "localization" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/localization into .opencode/skills/localization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "localization", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
localization- GitHub stars
- 2.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 617 words
- Files
- 1
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- MIT
At a glance
When the user wants to localize their App Store listing for international markets.
- Works in 3 steps: Research (per market) → Translation & Adaptation → Launch & Monitor
- Wants to localize their App Store listing for international markets
- SKILL.md covers Initial Assessment, Market Prioritization, Localization Checklist and Localization Workflow, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Localization is an agent skill from appeeky/aso-skills. 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.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Internationalization, App store release and Keyword research. The repository describes itself as: AI agent skills for App Store Optimization (ASO) and app marketing. Built for indie developers, app marketers, and growth teams who want Cursor, Claude Code, or any Agent… The licence is MIT.
When your agent uses it
- Wants to localize their App Store listing for international markets
- The user mentions localization
- Translate my app
- International markets
Example prompts
- “localization”
- “translate my app”
- “international markets”
- “/localization”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 3919d7c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Localization loads about 1.5k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 617 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from appeeky/aso-skills at commit 3919d7c, republished under its MIT licence (© appeeky). 617 words, ~1,515 tokens.
Download SKILL.mdSave it as
.claude/skills/localization/SKILL.md (or your agent's skills folder).- 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
- 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
Show full SKILL.md (239 more words)Show less
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
© appeeky, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/localization of appeeky/aso-skills.
Open the folder on GitHubat commit 3919d7c
Compare with similar skills
Localization next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Localization this skillappeeky/aso-skills | 2.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Asc Metadata Syncn0an/VivaDicta | 131 | 1 repos | ~1k | Automated safety check: Pass | MIT | |
| Asc Localize MetadataCamilleScholtz/swmpc | 239 | 5 repos | ~2.8k | Automated safety check: Pass | EUPL-1.2 | |
| Store Localizationdotnetdreamer/open-screenshot-generator | 124 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Krankie Auditn0an/VivaDicta | 131 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Chuhai Market Entrymohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Asc Localize Metadata
CamilleScholtz/swmpc
Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI.
Store Localization
dotnetdreamer/open-screenshot-generator
Ships one screenshot design in many App Store and Play Store languages using the open-screenshot-generator CLI (osg localize): it adds store locales to an existing project, writes per language copy…
Krankie Audit
n0an/VivaDicta
Run an ASO audit on canonical App Store metadata under ./metadata, then a krankie-based competitor keyword-gap analysis (no Astro subscription).
Chuhai Market Entry
mohitagw15856/pm-claude-skills
Plan a Chinese company's entry into an overseas market (出海): choose the market with evidence, then plan entity, payments, localisation, compliance, channels and team for the first twelve months.
Page Metadata
kostja94/marketing-skills
When the user wants a full-page metadata audit or implementation across discovery, search intent, title, description, canonical, robots, hreflang, Open Graph, Twitter Cards, code or CMS changes…
More from appeeky/aso-skills
All 39 skills in this repoAb Test Store Listing
appeeky/aso-skills
When the user wants to A/B test App Store product page elements to improve conversion rate.
Android Aso
appeeky/aso-skills
When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features.
App Analytics
appeeky/aso-skills
When the user wants to set up, interpret, or improve their app analytics and tracking.
App Clips
appeeky/aso-skills
When the user wants to implement, optimize, or use App Clips for app discovery and conversion.
App Icon Optimization
appeeky/aso-skills
When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse.
App Marketing Context
appeeky/aso-skills
When the user wants to create or update their app marketing context document.
Related
Categories
Questions about Localization
What does Localization do?
When the user wants to localize their App Store listing for international markets. Localization is an agent skill from appeeky/aso-skills. When the user wants to localize their App Store listing for international markets.
When should I use Localization?
Localization fits situations like: wants to localize their App Store listing for international markets; the user mentions localization; translate my app; international markets.
How do I install Localization in Claude Code?
Run `npx skills add appeeky/aso-skills --skill localization -a claude-code`. Or copy the skill folder (skills/localization in appeeky/aso-skills) into .claude/skills/localization in your project. Claude Code loads it when a task matches its description.
How do I install Localization in Codex?
Run `npx skills add appeeky/aso-skills --skill localization -a codex`. Or copy the skill folder (skills/localization in appeeky/aso-skills) into .agents/skills/localization in your project. Codex loads it when a task matches its description.
Can I use Localization in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add appeeky/aso-skills --skill localization -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/localization, .gemini/skills/localization, .github/skills/localization and .opencode/skills/localization in your project.
What does Localization need to run?
SKILL.md names no scripts, command-line tools or credentials: Localization is instructions for the agent only.
Does Localization access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Localization safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Localization use?
Localization is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Localization use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Localization?
Skills that share tags, products or a category with Localization: Asc Metadata Sync (n0an/VivaDicta, 131 stars), Asc Localize Metadata (CamilleScholtz/swmpc, 239 stars), Store Localization (dotnetdreamer/open-screenshot-generator, 124 stars) and Krankie Audit (n0an/VivaDicta, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Localization?
appeeky (a GitHub organization) maintains it in appeeky/aso-skills, which has 2,152 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 6, 2026.
Source: appeeky/aso-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.