Professional Translator Skill
Machine translation is literal; professional translation conveys meaning, tone, and intent the way a
native speaker would say it. This skill translates with attention to register (formal vs. casual), the
audience, and idiom — and flags the places where a straight translation would mislead and a localization
choice is needed instead. (For marketing copy that must land emotionally in-culture, use
transcreation; for adapting a whole product, localization-brief.)
Required Inputs
Ask for these only if they aren't already provided:
- The text and the source → target language (incl. regional variant where it matters — e.g. Simplified vs. Traditional Chinese, LATAM vs. European Spanish).
- Register / audience — formal (legal, business), neutral, or casual; who reads it.
- Context — what it is (email, contract, UI string, marketing, instructions) — it changes the choices.
- Glossary / do-not-translate terms — brand names, product terms, anything fixed.
Output Format
Translation: [source] → [target]
Translation — the natural, register-appropriate target text. Read as if originally written in the target language, not translated into it.
Translator's notes — the choices a careful translator would flag:
- Register/tone — how formality was handled (e.g. 您 vs. 你 in Chinese, tu vs. usted, keigo in Japanese).
- Untranslatable / adapted terms — what had no direct equivalent and how it was rendered.
- Localization flags — where a literal translation would be wrong or odd: idioms, dates/units/currency, examples, cultural references — and the adaptation made (or a 🔴 flag if the user must decide).
- Kept verbatim — brand names, code, identifiers, URLs, proper nouns (unchanged).
- Ambiguities — anything in the source open to interpretation, with the assumption made.
Quality Checks
Anti-Patterns
Based On
Professional translation practice — meaning-based (not literal) translation, register matching, and the translation-vs-localization distinction.
1---2name: professional-translator-23description: "Translate text professionally — preserving tone, register, and meaning, not word-for-word. Use when asked to translate a document, email, or content between languages, or to improve a literal/machine translation. Produces a natural, register-appropriate translation plus translator's notes on choices, untranslatable terms, and anything that needs localization rather than translation."4homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/professional-translator.html5metadata:6 source: https://skillmd.com/skills/mohitagw15856/professional-translator-27 openclaw:8 emoji: 🌐9---1011# Professional Translator Skill1213Machine translation is literal; professional translation conveys *meaning, tone, and intent* the way a14native speaker would say it. This skill translates with attention to register (formal vs. casual), the15audience, and idiom — and flags the places where a straight translation would mislead and a *localization*16choice is needed instead. (For marketing copy that must land emotionally in-culture, use17[`transcreation`](../transcreation/SKILL.md); for adapting a whole product, [`localization-brief`](../localization-brief/SKILL.md).)1819## Required Inputs2021Ask for these only if they aren't already provided:2223- **The text** and the **source → target language** (incl. regional variant where it matters — e.g. Simplified vs. Traditional Chinese, LATAM vs. European Spanish).24- **Register / audience** — formal (legal, business), neutral, or casual; who reads it.25- **Context** — what it is (email, contract, UI string, marketing, instructions) — it changes the choices.26- **Glossary / do-not-translate terms** — brand names, product terms, anything fixed.2728## Output Format2930### Translation: [source] → [target]3132**Translation** — the natural, register-appropriate target text. Read as if originally written in the target language, not translated into it.3334**Translator's notes** — the choices a careful translator would flag:35- **Register/tone** — how formality was handled (e.g. 您 vs. 你 in Chinese, tu vs. usted, keigo in Japanese).36- **Untranslatable / adapted terms** — what had no direct equivalent and how it was rendered.37- **Localization flags** — where a literal translation would be wrong or odd: idioms, dates/units/currency, examples, cultural references — and the adaptation made (or a 🔴 flag if the user must decide).38- **Kept verbatim** — brand names, code, identifiers, URLs, proper nouns (unchanged).39- **Ambiguities** — anything in the source open to interpretation, with the assumption made.4041## Quality Checks4243- [ ] Reads natural and idiomatic in the target language — not a literal word map44- [ ] Register/formality matches the audience and is noted (esp. you/formality distinctions)45- [ ] Brand names, code, identifiers, and URLs are kept unchanged46- [ ] Idioms, units, dates, and cultural references are adapted (or flagged), not translated literally47- [ ] Regional variant is respected where it matters48- [ ] Genuine ambiguities are surfaced, not silently guessed4950## Anti-Patterns5152- [ ] Do not translate word-for-word — convey meaning and tone the way a native would phrase it53- [ ] Do not ignore register — the wrong formality (over-familiar or stiff) can offend or undermine54- [ ] Do not translate idioms literally — render the equivalent expression or the plain meaning55- [ ] Do not translate brand/product/proper names or code — keep them verbatim56- [ ] Do not silently resolve ambiguity — flag it; the author may mean something specific5758## Based On5960Professional translation practice — meaning-based (not literal) translation, register matching, and the translation-vs-localization distinction.