baoyu-translate

Translate Markdown content between languages with three modes and glossary support.

54|18|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/open-fox/agents --skill baoyu-translate-open-fox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: baoyu-translate
Source: https://github.com/open-fox/agents/tree/main/skills/baoyu-translate
Command: npx skills add https://github.com/open-fox/agents --skill baoyu-translate-open-fox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires markdown-it, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Translates articles and documents between languages using a structured three-mode workflow: quick for direct translation, normal for analysis-then-translation, and refined for end-to-end publication-quality translation. It preserves Markdown formatting, supports custom glossaries via EXTEND.md to ensure terminology consistency, and provides a systematic workflow from analysis through polishing.

Core Features & Use Cases

  • Three-mode translation pipeline (quick, normal, refined) for Markdown content and other documents.
  • Glossary integration via EXTEND.md plus built-in references to ensure consistent terminology.
  • Chunking and prompt assembly to handle long texts, with per-chunk translation and cross-chunk consistency.
  • Extensible preferences via EXTEND.md (target language, mode, audience, style, glossaries) and a first-time setup when EXTEND.md is missing.
  • Use Cases: translating long articles, product docs, or multilingual guides while preserving structure.

Quick Start

Provide a Markdown source (URL, file, or inline text) and specify the target language and mode to begin translation.

Frequently Asked Questions about baoyu-translate

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

FAQPage Schema
How do I translate Markdown documents while preserving formatting and terminology?

You can translate Markdown documents using a three-mode workflow that preserves formatting and ensures terminology consistency via a custom glossary. The process handles long texts through chunking and cross-chunk consistency checks.

What is the best way to handle long article translation without breaking document structure?

Handling long article translation without breaking structure requires a tool with text chunking capabilities. The workflow processes content per chunk, translates sequentially, and enforces cross-chunk consistency to maintain document integrity.

Can I set up a custom glossary for consistent terminology across multiple translated articles?

Yes, you can set up a custom glossary for consistent terminology by using an EXTEND.md file. This file defines specific terms, target languages, audience preferences, and style guidelines to apply across all translations.

Does the Markdown translation workflow support different quality levels for quick drafts and publication-ready content?

The Markdown translation workflow supports different quality levels through three modes: quick for direct translation, normal for analysis-then-translation, and refined for end-to-end publication-quality output including drafting, review, and polishing stages.

How do I start localizing product documentation if I do not have a configuration file set up?

To start localizing product documentation without configuration, the workflow triggers a first-time setup process when the EXTEND.md file is missing. You simply provide a Markdown source and specify the target language and mode to begin.