agentleFS
Sign inStart free
vanthienha199vanthienha199/openclaw-skills/translate/SKILL.md

translate

Skill1 starsChanged 8 months agoMITView on GitHub

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".

49 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use faq, summarize and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    faq

    Turn repeat questions into a pinned FAQ. Use when a champion keeps answering the same questions.

    Also in 3 projects that use this

  • mitsuhikoSkill

    summarize

    Fetch a URL or convert a local file (PDF/DOCX/HTML/etc.) into Markdown using `uvx markitdown`, optionally it can summarize

    Also in 8 projects that use this

  • jacobraskSkill

    calendar

    Interact with Apple Calendar via AppleScript. Use when the user asks to check calendar, view events, create events, manage schedule, find free time, or list calendars. Triggers include "my calendar", "my schedule", "calendar events", "create event", "add to calendar", "what's on my calendar", "free time", "available slots", "upcoming events", "today's events". Requires macOS with Calendar.app.

    Also in 3 projects that use this

  • AnthropicSkill

    analyze

    Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.

    Also in 4 projects that use this

  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 5 projects that use this

  • VercelSkill

    publish

    Publish a single demo to v0 and optionally create Typefully drafts. Use when the user says "publish", "publish to v0", or "create typefully draft" for a demo.

    Also in 3 projects that use this

  • +2 more from anthropics

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 41 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user provides text and a target language, translate it.

    line 23
  2. Distinctive:

    Every English message → translate to Korean

    line 75
  3. Distinctive:

    Every Korean message → translate to English

    line 76
  4. Distinctive:

    When translating code files, ONLY translate comments and strings — never translate code:

    line 90
  5. Distinctive:

    Keep all code blocks untranslated

    line 98
  6. Distinctive:

    Keep URLs, paths, and commands untranslated

    line 99
  7. Distinctive:

    Keep the same structure

    line 101
  8. Distinctive:

    Never add your own content — only translate what's there

    line 107
  9. Distinctive:

    If a word has no good translation, keep the original in parentheses: "cocotb (cocotb)"

    line 108
  10. Distinctive:

    If unsure about context, ask before translating

    line 110
  11. Distinctive:

    Always show the language pair: "X → Y"

    line 111

“Common” is measured: kept by at least 6 in 10 of the 41 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free