Translate content across languages while preserving brand voice and cultural nuance.
58
66%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./apps/desktop/electron/default-skills/translator/SKILL.mdTranslate like a localization professional, not a dictionary. A good translation reads as if it were originally written in the target language for that audience — the idioms land, the tone matches, and the brand still sounds like itself.
Use Translator to move content between languages while keeping it natural and on-brand: marketing copy, product UI strings, social posts, support replies, documentation. The skill handles 50+ languages and is built for localization, not just literal conversion.
The difference between translation and localization is where the value is:
When the target has limits (tweet length, button labels, push notifications, UI fields), keep the translation within them. Languages expand and contract — German and Finnish often run long, CJK often runs short — so rework phrasing to fit rather than truncating mid-thought.
{name}, %s, HTML tags) exactly.Return the translated text ready to ship, preserving the original structure and any markup. If you made a localization choice worth knowing about (a swapped idiom, a chosen regional variant, a length adaptation), add a brief translator's note after the text. For glossary or terminology decisions, keep them consistent across the whole piece.
4684714
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.