translate

Translate content between English and Korean while preserving markdown formatting and code blocks.

37|7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/unclejobs-ai/second-claude-code --skill translate-unclejobs-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translate
Source: https://github.com/unclejobs-ai/second-claude-code/tree/main/skills/translate
Command: npx skills add https://github.com/unclejobs-ai/second-claude-code --skill translate-unclejobs-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of producing reliable English-to-Korean (and Korean-to-English) translations that keep formatting, technical accuracy, and intended voice—without breaking markdown structure or code snippets.

Core Features & Use Cases

  • Style-safe translation: Forces an explicit style mode (literal/natural/creative) to avoid inconsistent outputs and unintended localization.
  • Formatting preservation & adaptation: Preserves markdown structure and code fences in preserve mode, or adapts structure for cultural localization in adapt mode.
  • QA review loop: Performs a dedicated QA pass to verify accuracy, glossary compliance, and formatting integrity.
  • Glossary + soul-aware tone: Applies references/glossary.md term mappings and aligns voice with ## Tone Rules from .data/soul/SOUL.md when available.

Quick Start

Ask to translate the provided text from English to Korean in natural style while preserving the original markdown formatting.

Frequently Asked Questions about translate

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

FAQPage Schema
How do I translate markdown content between English and Korean without breaking formatting?

English to Korean markdown translation preserves markdown structure, code fences, and inline code snippets without breaking them. It processes technical prose, structured lists, and tables while passing a QA review loop to verify formatting integrity and glossary compliance.

What is the difference between literal, natural, and creative style modes for bilingual document translation?

Style modes for bilingual document translation force an explicit choice between literal, natural, and creative outputs to avoid inconsistent localization. Selecting a mode aligns the translated voice, ensuring predictable results for technical prose or localized content.

Can I use a custom glossary for English to Korean technical translation?

You can apply a custom glossary for English to Korean technical translation by mapping terms through references. The QA review loop verifies that the translated output complies with these glossary mappings for strict technical accuracy.

Does code block translation leave inline code and fenced code blocks untouched?

Code block translation strictly leaves inline code and fenced code blocks untouched. It translates technical prose around the code while preserving the original markdown formatting and code snippet syntax exactly as written.

What is the best way to adapt markdown structure for cultural localization?

Adapting markdown structure for cultural localization uses the adapt formatting mode to modify the original structure. This differs from preserve mode, allowing the document to align with cultural context while maintaining technical accuracy through a QA review loop.

When should I not use an automated markdown translation workflow?

You should not use an automated markdown translation workflow when your content lacks a defined style mode or requires translating inline code. The process requires explicit literal, natural, or creative mode selection and a QA pass to ensure glossary compliance.