translation

Translate text across languages while preserving register, idioms, and domain terminology.

2|Updated Jul 15, 2026
One-click install
npx skills add https://github.com/poorvith-mp/skills-writing --skill translation-poorvith-mp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: translation
Source: https://github.com/poorvith-mp/skills-writing/tree/main/skills/translation
Command: npx skills add https://github.com/poorvith-mp/skills-writing --skill translation-poorvith-mp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Machine translation often produces grammatically valid but unnatural, culturally inappropriate, or technically inaccurate output. This Skill provides a structured framework for translating content while preserving tone, register, idioms, and domain-specific terminology. ## Core Features & Use Cases - Terminology Standardization: Build Do Not Translate (DNT) lists and approved glossaries so brand names, API endpoints, and CLI commands stay untranslated. - Register & Cultural Calibration: Match formality levels (e.g., German Du/Sie, Japanese Keigo) and adapt idioms dynamically rather than literally. - Back-Translation QA: Verify high-stakes legal, medical, or brand content via independent back-translation to expose semantic drift. - Use Case: Localize English API documentation into Japanese, keeping code identifiers in ASCII while rendering error messages in polite Japanese software conventions. ## Quick Start Translate this technical documentation from English to German, preserving the informal developer register and keeping all CLI commands untranslated.

Frequently Asked Questions about translation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate technical documentation without breaking code examples?▼

Build a Do Not Translate list before translating that covers API endpoints, CLI commands, programming keywords, and brand names. Translate only the surrounding prose while keeping identifiers like `kubectl apply` or `git push` in their original form.

How to handle idioms and cultural references when translating?▼

Translate the underlying meaning rather than the literal words, a technique called dynamic equivalence. For example, render 'bite the bullet' as accepting an inevitable hardship in the target language instead of a literal ammunition metaphor.

What is back-translation and when should I use it?▼

Back-translation means having an independent linguist translate the target text back into the source language without seeing the original. Use it for high-stakes content like legal agreements, medical documentation, or core brand messaging to expose semantic drift.

Can machine translation output be used directly for professional content?▼

Raw machine translation output should not be released without human review. It often produces grammatically valid but unnatural or culturally offensive phrasing, and it may mistranslate domain terminology or translate code that must stay intact.

How do I choose the right formality level in languages like German or Japanese?▼

Match the register to your audience and content type. Use German 'Du' for developer documentation but 'Sie' for legal or banking text, and Japanese Keigo for formal business communication versus neutral Desu/Masu for technical docs.