← ClaudeAtlas

article-translatorlisted

Translate articles, essays, blog posts, threads, and other longer-form prose between any pair of languages while preserving the author's voice, register, and rhetorical structure. Use this whenever the user asks to translate, localize, render, or "give me in [language]" any text longer than a few paragraphs — news articles, op-eds, essays, blog posts, longreads, newsletters, technical writeups, conference transcripts, Twitter/X threads, or non-fiction excerpts. Trigger even when the user does not say the word "translate" explicitly — for example "I need this in English for our investors", "rewrite this for a Russian audience", or "make this readable to a German reader" all count. Do not use for single sentences, UI strings, code-only inputs, or short slogans — those are too small to benefit from this workflow.
Osipchuk/agent-skills · ★ 5 · AI & Automation · score 80
Install: claude install-skill Osipchuk/agent-skills
# Article Translator A workflow for translating long-form prose with fidelity, consistency, and a preserved authorial voice. Translation here is treated as a series of deliberate choices over a whole text — not a sentence-by-sentence transcoding. ## When to use Apply this skill whenever the input is **more than ~3 paragraphs of prose** and the user wants it rendered in another language. Typical inputs: news articles, op-eds, essays, blog posts, longreads, newsletter issues, conference transcripts, technical writeups, threads. Out of scope: UI copy, code, single sentences, tweet-sized fragments, song lyrics, metered poetry (literary verse translation needs a different toolkit), legal contracts (need specialized terminology and disclaimers). ## Core workflow at a glance 1. **Analyze** the source: language, locale, register, voice, purpose, and a brief structural outline of the argument. 2. **Build a glossary** of names, terms, numbers, dates, and recurring phrases — fixed renderings, applied throughout. 3. **Decide strategy** on idioms, units, punctuation, and format preservation. 4. **Translate** in paragraph-sized semantic units, never sentence-by-sentence. Maintain logical flow across paragraph seams. 5. **Footnote** sparingly — only for preserved-but-opaque expressions or load-bearing ambiguities. 6. **Self-review** against the criteria below: drift, omissions, additions, naturalness, register, style. **Priority order on conflicts:** accuracy → terminology consistenc