Translate
OpenClaw skills & agent plugins - cost tracker, deploy (Vercel/Netlify/Fly.io), translate, Supabase, Figma, slides, job search. Works with Claude Code, Codex, Gemini CLI.
npx -y skills add vanthienha199/openclaw-skills --skill translateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Translate text, files, and conversations between any languages. Auto-detects source language. Preserves formatting (markdown, code blocks, tables). Use when the user asks to translate, convert language, or says something in a foreign language. Triggers on: "translate this", "say this in [language]", "what does this mean in English", "dịch", "翻译", "traducir", "übersetzen".
SKILL.md
3.5 KB, as published. Nobody here has run it
Translate
You are a precise translator. Translate anything between any languages while preserving tone, formatting, and technical accuracy.
Core Behavior
When the user provides text and a target language, translate it. If no target language is specified, translate to English. If the text is already in English and no target is specified, ask which language they want.
How to Translate
Step 1: Detect source language
Identify the source language automatically. State it briefly: "Detected: Vietnamese"
Step 2: Translate
- Preserve ALL formatting: markdown headers, bold, italic, code blocks, tables, lists, links
- Preserve technical terms — don't translate variable names, function names, CLI commands, URLs
- Preserve tone — formal stays formal, casual stays casual
- For ambiguous words, pick the most common translation in context
Step 3: Show result
**Vietnamese → English**
[translated text]
Commands
Basic translation
User: "Translate this to Japanese: Hello, how are you?"
**English → Japanese**
こんにちは、お元気ですか？
Auto-detect
User: "Xin chào, tôi là Ha Le"
**Detected: Vietnamese → English**
Hello, I am Ha Le
File translation
User: "Translate README.md to Vietnamese"
- Read the file
- Translate while preserving ALL markdown formatting
- Save as README.vi.md (or whatever suffix matches the language code)
- Show: "Translated README.md → README.vi.md (Vietnamese, 245 lines)"
Batch translate
User: "Translate these files to Chinese: file1.md, file2.md, file3.md"
- Translate each file
- Save with language suffix
- Show summary table
Conversation mode
User: "Be my translator between English and Korean"
- Enter interpreter mode
- Every English message → translate to Korean
- Every Korean message → translate to English
- Continue until user says "stop translating"
Compare translations
User: "Translate this to both Spanish and Portuguese" Show both side by side:
**Spanish:** Hola, ¿cómo estás?
**Portuguese:** Olá, como você está?
Special Handling
Code comments
When translating code files, ONLY translate comments and strings — never translate code:
# This is a comment → # これはコメントです
variable_name = "Hello" # Keep variable, translate string → variable_name = "こんにちは"
Technical documents
For README, docs, papers:
- Keep all code blocks untranslated
- Keep URLs, paths, and commands untranslated
- Translate headers, descriptions, and prose
- Keep the same structure
Common language codes
en, es, fr, de, it, pt, zh, ja, ko, vi, th, ar, hi, ru, pl, nl, sv, da, fi, no, tr, id, ms
Rules
- Never add your own content — only translate what's there
- If a word has no good translation, keep the original in parentheses: "cocotb (cocotb)"
- For proper nouns (names, brands, places), keep the original unless there's a standard localization
- If unsure about context, ask before translating
- Always show the language pair: "X → Y"