Translate

Translate text between languages while preserving formatting, placeholders, and locale conventions.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/HalseyYang/Skills-HY --skill translate-halseyyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Translate
Source: https://github.com/HalseyYang/Skills-HY/tree/main/translate
Command: npx skills add https://github.com/HalseyYang/Skills-HY --skill translate-halseyyang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Translating content often breaks formatting, corrupts placeholders, or produces literal translations that ignore cultural context. This Skill ensures translations preserve markdown structure, code blocks, and variables while adapting tone, plurals, and idioms to the target locale. ## Core Features & Use Cases - Formatting Preservation: Keeps code blocks, HTML tags, markdown syntax, and placeholders like {name} or %s untouched during translation. - Locale-Aware Adaptation: Handles plural rules, grammatical gender, formality registers (tu/vous, du/Sie), date formats, and unit conversions per target language. - Cultural & Contextual Accuracy: Adapts idioms rather than translating literally, disambiguates terms by context, and maintains consistent terminology via glossaries. - Use Case: Translate a product's markdown documentation from English to German while keeping all code samples, API endpoints, and brand names intact, with formal "Sie" register and DD.MM.YYYY date formats. ## Quick Start Translate this markdown document into French, preserving all code blocks, placeholders, and formatting while using formal register.

Frequently Asked Questions about Translate

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

FAQPage Schema
How do I translate markdown files without breaking formatting?

Translate only the prose content while leaving markdown syntax, headers, links, and bold/italic markers untouched. Code blocks, HTML tags, and placeholders like {name} or %s must remain exactly as-is so the document structure stays functional.

How to handle placeholders and variables when translating software strings?

Preserve placeholders such as {name}, {{variable}}, %s, and $1 verbatim in the translated output. Only translate the surrounding natural language text, and verify placeholder positions still make grammatical sense in the target language.

What should not be translated in technical documentation?

Do not translate proper nouns, brand names, technical terms, URLs, email addresses, code snippets, CSS classes, API endpoints, or file extensions. Numbers, dates, and IDs stay in original format unless locale conversion is explicitly needed.

Does translation need to handle plural forms differently per language?

Yes, each language has its own plural rules that differ from English patterns. Gendered languages like Spanish, French, and German also require noun-adjective agreement, and formality registers such as tu/vous or du/Sie must match the context.

Why do literal translations of idioms cause problems?

Idioms rarely carry meaning across languages when translated word-for-word, producing confusing or nonsensical output. Adapt expressions to culturally equivalent phrases in the target language while preserving the original intent and emotional nuance.