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". For keyword research in specific markets, see keyword-research. For metadata writing, see metadata-optimization.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/localization/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, information-dense skill body with concrete ASO specifics and a clear three-phase workflow. The main improvement opportunities are moving the market-tier reference tables to a bundle file, tightening the persona opener, and specifying how to execute the monitoring steps.

Suggestions

Move the Tier 1/Tier 2 market tables into a references/ file (e.g. references/markets.md) and keep a short decision framework inline, which would push progressive disclosure toward the top anchor.

Specify the tool or method for Phase 3 monitoring (e.g. 'run keyword-research weekly per market and compare rankings') so every step is executable rather than directional.

Trim the 'You are an expert in...' opener and generic cultural rows ('Diverse representation, culturally appropriate') to reclaim tokens without losing clarity.

Dimension	Reasoning	Score
Conciseness	The body is dense with non-obvious domain data (char limits, locale codes, weighted scoring factors, per-language keyword examples) and explains almost nothing Claude already knows; only minor trimmable padding remains, like the 'You are an expert in...' persona opener and a few generic cultural-adaptation rows.	4 / 5
Actionability	Concrete, executable guidance throughout — exact character limits (30/30/100/4000/170), App Store locale codes, a weighted market-scoring table, and a copy-paste output template. It falls short of fully executable because a few steps ('Monitor keyword rankings (weekly)', 'Track conversion rate by country') don't specify the tool or method.	4 / 5
Workflow Clarity	Three numbered phases with a clear sequence and some explicit checkpoints ('Review with keyword data — does the translation include high-volume terms?', 'Iterate based on performance data'). Not a 5: the Initial Assessment answers aren't explicitly wired into the prioritization step, and Phase 3 monitoring lacks validation criteria for when to iterate.	4 / 5
Progressive Disclosure	No bundle files exist and the single-file body is well-sectioned with clear headers and a related-skills section. At ~165 lines it exceeds the simple-skill exception, and the Tier 1/Tier 2 market tables are reference-like content that could be split out — good structure with minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit what/when structure, useful cross-references to sibling skills, and natural trigger phrases. Its main weakness is thin capability coverage — it names localization of the store listing but not market prioritization or per-market keyword adaptation.

Suggestions

Enumerate 2-3 more concrete capabilities in the opening sentence, e.g. 'Prioritizes target markets, adapts metadata and keywords per locale, and plans cultural adaptation of screenshots' — this would lift specificity from the 1-2-action level to several-actions coverage.

Add 'App Store', 'localize my app listing', and 'other languages' to the trigger phrase list to cover the most common user phrasings and further reduce overlap with generic translation requests.

Dimension	Reasoning	Score
Specificity	The description names the domain ('localize their App Store listing for international markets') with essentially one concrete action, matching the anchor for 'names domain and 1-2 concrete actions, but not comprehensive' — it doesn't list the skill's other capabilities like market prioritization, keyword adaptation per market, or cultural adaptation.	3 / 5
Completeness	It explicitly answers both what ('localize their App Store listing for international markets') and when ('Also use when the user mentions...') with concrete trigger phrases, matching the top anchor exactly; the 'when' is fully explicit, not merely present.	5 / 5
Trigger Term Quality	Six natural quoted trigger phrases ('translate my app', 'expand to new countries', 'which countries should I target') give good coverage, but common variants like 'App Store', 'other languages', or 'localize my app' are missing, so it falls just short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	It carves a clear App Store niche and explicitly disambiguates from sibling skills ('For keyword research... see keyword-research'), but 'translate my app' could plausibly fire for app-UI translation rather than store-listing localization — a minor overlap risk that keeps it just below the minimal-conflict anchor.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Eronred/aso-skills
Path: skills/localization/SKILL.md
Commit: 8de1ee1

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.