CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

The body is a well-structured, actionable localization playbook with concrete tables, character limits, a weighted prioritization framework, and a clear three-phase workflow including a launch feedback loop. Improvements would be tightening a few explanatory asides and adding explicit validation checkpoints between phases.

Suggestions

Add explicit validation gates between workflow phases (e.g., 'Confirm metadata char limits pass before submitting each market') to strengthen the feedback loop for batch multi-market localization.

Trim inferable asides (e.g., the red=luck/danger color note, 'Understand how locals search') to improve conciseness, or move the Tier 1/2 market tables and cultural-adaptation table into reference files for cleaner progressive disclosure.

Tighten the description's capability list to mention market prioritization and cultural adaptation explicitly so specificity matches the breadth the body actually delivers.

DimensionReasoningScore

Conciseness

Mostly efficient with compact high-signal tables and a clear template; minor padding such as the cultural color aside and restated guidance that Claude could largely infer.

4 / 5

Actionability

Concrete and actionable for an instruction-only skill: specific char limits, market codes, a weighted scoring framework, and a copy-ready output template, with only minor gaps in executable specifics.

4 / 5

Workflow Clarity

Clear sequenced workflow (Initial Assessment → Prioritization → Research/Translation/Launch phases) with a launch-phase feedback loop (monitor, track, iterate); lacks explicit validation gates between phases.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with an inline output template; market and cultural reference tables are inlined rather than split into separate files, a minor organization gap given the body length.

4 / 5

Total

16

/

20

Passed

Description

90%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, abundant natural trigger phrases, and clear boundary guidance via redirects to adjacent skills. The only minor gap is specificity, since the description lists the domain and a couple of actions rather than comprehensively enumerating the skill's capabilities.

DimensionReasoningScore

Specificity

Names the domain (App Store listing localization) and 1-2 concrete actions ("localize their App Store listing", "localize metadata") but is not comprehensive about the full set of actions the skill performs.

3 / 5

Completeness

Explicitly answers both what (localize App Store listing for international markets) and when ("Also use when the user mentions..." with concrete trigger phrases).

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage with six user-realistic phrases including synonyms ("localization", "translate my app", "international markets", "expand to new countries", "localize metadata", "which countries should I target").

5 / 5

Distinctiveness Conflict Risk

Clear niche in App Store localization with explicit de-conflict redirects to keyword-research and metadata-optimization, minimizing wrong-skill triggering.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Eronred/aso-skills
Reviewed

Table of Contents

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.