baoyu-translate
Skill27k starsChanged 6 months agoMITView on GitHub
This skill should be used when the user asks to "translate", "翻译", "精翻", "translate article", "translate to Chinese", "translate to English", "改成中文", "改成英文", "convert to Chinese", "localize", "本地化", "refined translation", "精细翻译", "proofread translation", "快速翻译", "快翻", "这篇文章翻译一下", or provides a URL/file with translation intent. Supports three modes (quick/normal/refined) with custom glossary support.
4 other projects use a version of this, 4 of them edited; 4 of 4 edited versions we compared changed its rules.
How people change it
4 of 4 edited versions changed its rules, and some changes recur.
Of the 4 edited versions we compared: 4 made changes of their own.
Rules people drop
- Check EXTEND.md (see Preferences)dropped by 4 of 4
- All intermediate and final files go in the output directory:dropped by 4 of 4
- Quick mode never chunks. If content exceeds the chunk threshold, warn: "This article is ~{N} words. …dropped by 4 of 4
- Assemble prompt: read
01-analysis.md(if it exists) and build shared context with Part 1 of [references/subagent-prompt-template.md](references/subagent-prompt-template.md), inlining target style, content background, merged glossary, and translation …dropped by 4 of 4 - Keep all intermediate files in
chunks/dropped by 4 of 4 - After merging, the main agent takes over for review, revision, and polish (Step 4).dropped by 4 of 4
- Rewrite, not translate: write natural, engaging target language as if a skilled native writer composed it. Test: "Does this read like it was originally written in the target language?"dropped by 4 of 4
- When this skill prompts the user, follow this tool-selection rule (priority order):dropped by 3 of 4
Rules people add
- A rule we can't quote: its licence doesn't allow itadded by 4 of 4
- A rule we can't quote: its licence doesn't allow itadded by 4 of 4
- A rule we can't quote: its licence doesn't allow itadded by 4 of 4
- A rule we can't quote: its licence doesn't allow itadded by 4 of 4
- A rule we can't quote: its licence doesn't allow itadded by 4 of 4
- A rule we can't quote: its licence doesn't allow itadded by 4 of 4
- A rule we can't quote: its licence doesn't allow itadded by 4 of 4
- A rule we can't quote: its licence doesn't allow itadded by 4 of 4
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- AgnesAI-Labs/agnet-skills-cnedited, first seen Nov 1, 2026
- eugeneli326/claude-skillsedited, first seen Oct 13, 2026
- SwimmingLiu/easy-skillsedited, first seen Aug 16, 2026
- YuppyChen/ai-wechatedited, first seen Mar 19, 2026
Who's talking about JimLiu/baoyu-skills
- 宝玉的技术分享“Agent Skills 设计哲学和实战进化”YouTube · Mar 23, 2026 · 2k views
- Yangjin | AI, Life & Business“我让 Codex 找 GitHub Skill,为什么一个都没直接装?”YouTube · Jul 19, 2026 · 1.4k views
- GitHub Trending Digest“baoyu-skills - GitHub Trending Today”YouTube · Apr 11, 2026 · 236 views
- Find Interesting AI“OPC时代—程序员的营销基础、工具选择、学习建议”YouTube · Jul 5, 2026 · 150 views
- AI워크랩“ChatGPT 보고서 꾸미기 스킬 5개 설치해 써 봤다 — Word 서식 · 테마 10종 · PPT 10장 | GitHub 인기 스킬”YouTube · Oct 21, 2026 · 114 views
The biggest 5 of 66 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 66
Talked about on GitHub, YouTube, Bluesky and the web (66 times).
On GitHub · 50
- Nov 7, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Nov 7, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Nov 6, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Nov 6, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Nov 5, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
45 more on GitHub
- Nov 5, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Nov 4, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Nov 4, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Nov 3, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Nov 3, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Nov 2, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Nov 2, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Nov 1, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Nov 1, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 31, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 31, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 30, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 30, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 29, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 29, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 28, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 28, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 27, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 27, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 26, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 26, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 25, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 25, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 24, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 24, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 23, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 23, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 22, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 22, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 21, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 21, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 20, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 20, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 19, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 19, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 18, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 18, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 17, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 17, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 16, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 16, 2026candidate: baoyu-post-to-wechat — BigPengSays/awesome-creator-skills0 reactions
- Oct 15, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 14, 2026candidate: baoyu-wechat-summary — BigPengSays/awesome-creator-skills0 reactions
- Oct 5, 2026[Candidate] jimliu/baoyu-skills/skills/baoyu-compress-image - baoyu-compress-image — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 5, 2026[Candidate] jimliu/baoyu-skills/skills/baoyu-comic - baoyu-comic — ProSkillsMD/proskills0 reactions · 1 comment
On YouTube · 12
- Mar 23, 2026Agent Skills 设计哲学和实战进化 — 宝玉的技术分享2k views · 5 comments
- Jul 19, 2026我让 Codex 找 GitHub Skill,为什么一个都没直接装? — Yangjin | AI, Life & Business1.4k views
- Apr 11, 2026baoyu-skills - GitHub Trending Today — GitHub Trending Digest236 views
- Jul 5, 2026OPC时代—程序员的营销基础、工具选择、学习建议 — Find Interesting AI150 views · 2 comments
- Oct 21, 2026ChatGPT 보고서 꾸미기 스킬 5개 설치해 써 봤다 — Word 서식 · 테마 10종 · PPT 10장 | GitHub 인기 스킬 — AI워크랩114 views
7 more on YouTube
- May 19, 2026Skills profissionais para Claude Code, Codex, Gemini e Cursor #AI #Shorts — RepoShots105 views · 1 comment
- Mar 11, 2026baoyu-skills hit 9.4K GitHub stars #BaoyuSkills #AgentSkills #ClaudeSkills #CodexSkills #Shorts — Pulse100 views · 1 comment
- May 19, 2026ClaudeCode 实战应用-打通公众号从配图、排版到推送到草稿箱,一气呵成,不再被编辑器束缚 — NicknickAI59 views
- Oct 28, 2026baoyu-skills: This AI agent can create new skills while it works — HubMesh40 views
- Oct 26, 20263 skills de Claude que convierten tu texto en cómics e infografías 🎨 — BarbuPrime IA | Claude Code Vs Codex14 views · 1 comment
- Oct 24, 2026一张产品图,做出两版醒目封面 — 慢半拍的安迪鲁14 views
- Oct 24, 2026用Codex把一页说明变成六步上手图|相机入门 #Shorts — 慢半拍的安迪鲁14 views
On Bluesky · 3
- Aug 11, 2026📦 JimLiu / baoyu-skills ⭐ 24,846 (+50) 🗒 TypeScript — @github-trending-js.bsky.social1 likes and repost
- Apr 11, 2026🔥 Hot Repo! 🔥 (100+ new stars) 📦 JimLiu / baoyu-skills ⭐ 14,102 (+111) 🗒 TypeScript — @github-trending-js.bsky.social1 likes and repost
- Feb 20, 2026https://github.com/JimLiu/baoyu-skills — @tom-doerr.bsky.social1 likes and repost
On the web · 1
- Nov 2, 2026baoyu-infographic Skill: Turn Text into Infographics | PlugWiki — plugwiki.com
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- YuppyChen/ai-wechat★ 6530% same
- AgnesAI-Labs/agnet-skills-cn★ 148% same
- SwimmingLiu/easy-skills★ 129% same
- eugeneli326/claude-skills★ 031% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- release-skillsSkill
- baoyu-article-illustratorSkill
- baoyu-comicSkill
- baoyu-compress-imageSkill
- baoyu-cover-imageSkill
- baoyu-danger-gemini-webSkill
- baoyu-danger-x-to-markdownSkill
- baoyu-diagramSkill
- baoyu-electron-extractSkill
- baoyu-format-markdownSkill
- baoyu-image-genSkill
- baoyu-infographicSkill
- baoyu-markdown-to-htmlSkill
- baoyu-post-to-wechatSkill
- baoyu-post-to-weiboSkill
- baoyu-post-to-xSkill
- baoyu-slide-deckSkill
- baoyu-url-to-markdownSkill
- baoyu-wechat-summarySkill
- baoyu-xhs-imagesSkill
- baoyu-youtube-transcriptSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 3 are common, 8 are distinctive, and 3 are very specific to this project.
3
Common
Most of the 4 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
When this skill prompts the user, follow this tool-selection rule (priority order):
- Distinctive: line 26
Fallback: if no such tool exists, emit a numbered plain-text message and ask the user to reply with the chosen number/answer for each …
- Distinctive: line 27
Batching: if the tool supports multiple questions per call, combine all applicable questions into a single call.
- Distinctive: line 105
Check EXTEND.md (see Preferences)
- Distinctive: line 113
All intermediate and final files go in the output directory:
- Distinctive: line 127
Quick mode never chunks: If content exceeds the chunk threshold, warn: "This article is ~{N} words.
- Very specific: line 136
Assemble prompt: read 01-analysis.md (if it exists) and build shared context with Part 1 of references/subagent-prompt-template.md, …
- Common: line 140
No chunks (under threshold): one subagent for the whole source file
- Very specific: line 141
No Agent tool: translate chunks sequentially inline using 02-prompt.md
- Very specific: line 143
Keep all intermediate files in chunks/
- Distinctive: line 145
After merging, the main agent takes over for review, revision, and polish (Step 4).
- Distinctive: line 151
Rewrite, not translate: write natural, engaging target language as if a skilled native writer composed it.
- Common: line 155
Preserve format: all markdown formatting (headings, bold, italic, images, links, code blocks)
- Common: line 201
If candidates were found, append after the summary a short note that some embedded images may still need image-text localization, followed …
“Common” is measured: kept by at least 6 in 10 of the 4 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.
Files
Translator
User Input Tools
When this skill prompts the user, follow this tool-selection rule (priority order):
- Prefer built-in user-input tools exposed by the current agent runtime — e.g.,
AskUserQuestion,request_user_input,clarify,ask_user, or any equivalent. - Fallback: if no such tool exists, emit a numbered plain-text message and ask the user to reply with the chosen number/answer for each question.
- Batching: if the tool supports multiple questions per call, combine all applicable questions into a single call; if only single-question, ask them one at a time in priority order.
Concrete AskUserQuestion references below are examples — substitute the local equivalent in other runtimes.
Script Directory
{baseDir} = this SKILL.md's directory. ${BUN_X} = bun if installed; else npx -y bun if npx available; else suggest installing bun. Replace {baseDir} and ${BUN_X} with actual values.
| Script | Purpose |
scripts/main.ts | CLI entry point. Default action splits markdown into chunks; also supports explicit chunk subcommand |
scripts/chunk.ts | Markdown chunking implementation used by main.ts and kept compatible for direct invocation |
Preferences (EXTEND.md)
First one found wins:
| Priority | Path | Scope |
| 1 | .baoyu-skills/baoyu-translate/EXTEND.md | Project |
| 2 | ${XDG_CONFIG_HOME:-$HOME/.config}/baoyu-skills/baoyu-translate/EXTEND.md | XDG |
| 3 | $HOME/.baoyu-skills/baoyu-translate/EXTEND.md | User home |
- Found → read and apply. On first use in a session, remind briefly: "Using preferences from [path]. You can edit EXTEND.md to customize glossary, audience, etc."
- Not found → BLOCKING first-time setup before any translation; never silently use defaults. Ask all questions in references/config/first-time-setup.md (target language, mode, audience, style, save location) in ONE call, write EXTEND.md at the chosen location, confirm "Preferences saved to [path]", then continue.
Supports: target language, mode, audience, glossaries (inline or file path), style, chunk settings. Schema: references/config/extend-schema.md.
Defaults
EXTEND.md overrides defaults; CLI flags override EXTEND.md.
| Setting | Default | EXTEND.md key | CLI flag |
| Target language | zh-CN | target_language | --to |
| Mode | normal | default_mode | --mode |
| Audience | general | audience | --audience |
| Style | storytelling | style | --style |
| Chunk threshold (words, triggers chunking) | 4000 | chunk_threshold | — |
| Chunk max words | 5000 | chunk_max_words | — |
Modes
| Mode | Flag | Steps | When to Use |
| Quick | --mode quick | Translate | Short texts, informal content, quick tasks |
| Normal | --mode normal (default) | Analyze → Translate | Articles, blog posts, general content |
| Refined | --mode refined | Analyze → Translate → Review → Polish | Publication-quality, important documents |
Auto-detection: "快翻", "quick", "直接翻译" → quick; "精翻", "refined", "publication quality", "proofread" → refined; otherwise the default mode.
Style presets (voice and tone, independent of audience; custom descriptions accepted, e.g. --style "poetic and lyrical"):
| Value | Description | Effect |
storytelling | Engaging narrative flow (default) | Draws readers in, smooth transitions, vivid phrasing |
formal | Professional, structured | Neutral tone, clear organization, no colloquialisms |
technical | Precise, documentation-style | Concise, terminology-heavy, minimal embellishment |
literal | Close to original structure | Minimal restructuring, preserves source sentence patterns |
academic | Scholarly, rigorous | Formal register, complex clauses OK, citation-aware |
business | Concise, results-focused | Action-oriented, executive-friendly, bullet-point mindset |
humorous | Preserves and adapts humor | Witty, playful, recreates comedic effect in target language |
conversational | Casual, spoken-like | Friendly, approachable, as if explaining to a friend |
elegant | Literary, polished prose | Aesthetically refined, rhythmic, carefully crafted word choices |
Audience presets (custom descriptions accepted, e.g. --audience "AI感兴趣的普通读者"):
| Value | Description | Effect |
general | General readers (default) | Plain language, more translator's notes for jargon |
technical | Developers / engineers | Less annotation on common tech terms |
academic | Researchers / scholars | Formal register, precise terminology |
business | Business professionals | Business-friendly tone, explain tech concepts |
Workflow
Step 1: Load Preferences
- Check EXTEND.md (see Preferences)
- Load the built-in glossary for the language pair if available — EN→ZH: references/glossary-en-zh.md
- Merge glossaries: EXTEND.md
glossary(inline) +glossary_files(paths relative to EXTEND.md) + built-in +--glossaryfile (CLI overrides all)
Step 2: Materialize Source & Create Output Directory
Materialize the source (file as-is; inline text/URL → translate/{slug}.md), then create {source-dir}/{source-basename}-{target-lang}/. Detect source language if --from is not given. Details and conflict handling: references/workflow-mechanics.md.
All intermediate and final files go in the output directory:
| File | Mode | Description |
translation.md | All | Final translation (always this name) |
01-analysis.md | Normal, Refined | Content analysis (domain, tone, terminology) |
02-prompt.md | Normal, Refined | Assembled translation prompt |
03-draft.md | Refined | Initial draft before review |
04-critique.md | Refined | Critical review findings (diagnosis only) |
05-revision.md | Refined | Revised translation based on critique |
chunks/ | Chunked | Source chunks + translated chunks |
Step 3: Assess Content Length
Quick mode never chunks. If content exceeds the chunk threshold, warn: "This article is ~{N} words. Quick mode translates in one pass without chunking — for long content, --mode normal produces better results with terminology consistency." Proceed if the user doesn't switch.
Normal/refined: below threshold → translate as a single unit; at or above → chunked translation (3.1).
3.1 Long Content Preparation (normal/refined, ≥ threshold)
- Extract terminology across the whole document (proper nouns, technical terms, recurring phrases)
- Build session glossary: merge extracted terms with loaded glossaries, fix consistent translations
- Split:
${BUN_X} {baseDir}/scripts/main.ts <file> [--max-words <chunk_max_words>] [--output-dir <output-dir>]— splits at markdown block boundaries (headings, paragraphs, lists, code blocks, tables, etc.); an oversized single block falls back to line, then word splitting - Assemble prompt: read
01-analysis.md(if it exists) and build shared context with Part 1 of references/subagent-prompt-template.md, inlining target style, content background, merged glossary, and translation challenges. Save as02-prompt.md(shared context only, no task instructions) - Draft via subagents (if an Agent tool is available):
- One subagent per chunk, all in parallel (Part 2 of the template). Each reads
02-prompt.md, gets its position (chunk N of M + brief context of where it sits in the argument), and saveschunks/chunk-NN-draft.md - Consistency comes from the shared
02-prompt.md(glossary, figurative language mapping, comprehension challenges, source voice, translation challenges) - No chunks (under threshold): one subagent for the whole source file
- No Agent tool: translate chunks sequentially inline using
02-prompt.md
- One subagent per chunk, all in parallel (Part 2 of the template). Each reads
- Merge chunks in order after all subagents finish; prepend
chunks/frontmatter.mdif it exists. Save as03-draft.md(refined) ortranslation.md(normal) - Keep all intermediate files in
chunks/
After merging, the main agent takes over for review, revision, and polish (Step 4).
Step 4: Translate & Refine
Translation principles (all modes):
- Rewrite, not translate: write natural, engaging target language as if a skilled native writer composed it. Test: "Does this read like it was originally written in the target language?"
- Accuracy first: facts, data, and logic match the original exactly
- Natural flow: idiomatic target word order; break long source sentences into shorter ones; render metaphors and idioms by intended meaning, not word-for-word
- Terminology: standard translations, used consistently; annotate specialized terms with the original in parentheses on first occurrence
- Preserve format: all markdown formatting (headings, bold, italic, images, links, code blocks)
- Proactive interpretation: for jargon or concepts the audience may lack context for, add concise explanations in bold parentheses
(**解释**)— few, only where genuinely needed - Frontmatter (if the source has YAML frontmatter): rename source-metadata fields with a
sourceprefix (camelCase:url→sourceUrl,title→sourceTitle, etc.), add translated values as new top-level fields (skiptitleif the body has an H1), keep other fields as-is
Quick: translate directly → translation.md.
Normal:
- Analyze →
01-analysis.md(domain, tone, terminology, translation challenges) - Assemble prompt →
02-prompt.md(instructions with context, glossary, challenges) - Translate following
02-prompt.md→translation.md
Then tell the user: "Translation saved. To further review and polish, reply 继续润色 or refine." If they do, run refined Steps 4-6 on the existing output: rename current translation.md to 03-draft.md, then write 04-critique.md, 05-revision.md, and an updated translation.md.
Refined — per-step guidelines in references/refined-workflow.md. Each step reads the previous step's file:
- Analyze →
01-analysis.md - Assemble prompt →
02-prompt.md(instructions with inlined context) - Draft →
03-draft.md(with translator's notes; from subagents if chunked) - Critical review →
04-critique.md(diagnosis only: accuracy, Europeanized language, strategy execution, expression issues) - Revision →
05-revision.md(apply all critique findings) - Polish →
translation.md(publication quality)
Subagents (Step 3.1) only produce the initial draft. Review, revision, and polish belong to the main agent, which may delegate to subagents at its discretion.
Step 5: Output
Final translation is always translation.md in the output directory.
Then run a lightweight image-language pass: collect image references, identify likely text-heavy ones (covers, screenshots, diagrams, charts, frameworks, infographics), and list any whose main text language likely differs from the translated article. List only — do not localize images unless the user asks. Use the article's own image syntax (markdown or wikilink):
Possible image localization needed:
- : likely still contains source-language text while the article is now in target language
- : likely text-heavy framework graphic, check whether labels need translationSummary:
**Translation complete** ({mode} mode)
Source: {source-path}
Languages: {from} → {to}
Output dir: {output-dir}/
Final: {output-dir}/translation.md
Glossary terms applied: {count}If candidates were found, append after the summary a short note that some embedded images may still need image-text localization, followed by the list.
Extension Support
Custom configurations via EXTEND.md — see Preferences above.
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
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.

