software-localization

Routes translation and i18n tasks to specialized localization sub-skills.

3|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill software-localization-jose-polanco-oxte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-localization
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/localization/sub-skills/software-localization
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill software-localization-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing software translations involves many distinct tasks — adding languages, syncing deltas, extracting hardcoded strings, reviewing quality — and it is hard to know which workflow applies to a given i18n request. ## Core Features & Use Cases - Task Routing: Maps a translation request to one of seven task-specific sub-skills (add-language, convert, extract, guide, health, review, sync) so only the relevant instructions are loaded. - Context Budget Control: Loads only the sub-skill needed for the current task instead of the entire localization workflow set. - Config Awareness: Directs sub-skills to honor .translation-sync.json settings such as sourceLanguage, targetLanguages, tone, and glossary. - Use Case: When asked to "sync the French translations after editing en.json", this skill identifies translation-sync as the matching sub-skill and points the agent to its SKILL.md. ## Quick Start Ask the agent to handle a translation task such as adding a new language or auditing translation coverage, and it will load the matching translation sub-skill.

Frequently Asked Questions about software-localization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right translation workflow for my i18n task?

Match your task to the routing table: adding a language uses translation-add-language, updating changed keys uses translation-sync, finding hardcoded strings uses translation-extract, and auditing coverage uses translation-health. Load only that sub-skill's SKILL.md.

What translation file formats are supported by these localization sub-skills?

The sub-skills support JSON, YAML, PO/Gettext, XLIFF, ARB, and Java Properties formats. The translation-convert sub-skill handles migration between these formats while preserving keys, variables, and pluralization rules.

Does this skill translate files by itself?

No. It is a grouping router with no standalone procedure. It identifies which translation-* sub-skill matches your task and directs the agent to load that sub-skill's SKILL.md, which contains the actual workflow.

How does the .translation-sync.json config affect localization tasks?

Several sub-skills read .translation-sync.json for sourceLanguage, targetLanguages, tone, and glossary settings. When present, these fields are honored so translations follow configured formality and terminology mappings.

When should I load multiple translation sub-skills at once?

Only when the task genuinely spans multiple areas, such as extracting strings and then syncing them. The skill explicitly recommends loading only the sub-skills the current task needs to conserve context budget.