Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Translate text accurately — preserve formatting, handle plurals, and adapt tone per locale.
Translate text accurately — preserve formatting, handle plurals, and adapt tone per locale.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Master accurate translation that preserves meaning, formatting, and cultural context.
Never translate content inside code blocks, HTML tags, or markdown syntax Preserve placeholders like {name}, {{variable}}, %s, $1 exactly as-is Keep markdown structure intact: headers, links, bold/italic formatting Maintain JSON/XML structure and keys — translate only values where appropriate
Don't translate: proper nouns, brand names, technical terms, URLs, email addresses Don't translate: code snippets, CSS classes, API endpoints, file extensions Preserve numbers, dates, and IDs in their original format unless locale conversion needed Keep consistent terminology throughout — create a glossary for repeated terms
Plurals: Use correct plural forms per target language rules (not English patterns) Gender: Ensure noun-adjective agreement in gendered languages (Spanish/French/German) Formality: Choose appropriate register (tu/vous, tú/usted, du/Sie) based on context RTL languages: Consider text direction for Arabic/Hebrew but keep LTR elements (URLs, numbers)
Adapt idioms and expressions rather than literal translation Convert units when culturally appropriate (miles↔km, Fahrenheit↔Celsius) Adjust date formats to locale standards (MM/DD vs DD/MM vs DD.MM) Use local currency symbols and number formatting (, vs . for decimals)
Disambiguate based on context: "bank" (financial vs river), "mouse" (animal vs computer) Maintain document tone: formal business vs casual blog vs technical manual Consider target audience: children's content vs academic paper vs marketing copy Preserve original intent and emotional nuance, not just literal meaning
Read full context before translating to understand meaning Check that translated text flows naturally in target language Verify all formatting elements remain functional after translation Ensure consistent voice and terminology across the entire document
Writing, remixing, publishing, visual generation, and marketing content production.
Largest current source with strong distribution and engagement signals.