Translate English Markdown files while preserving formatting and frontmatter semantics.
npx skills add https://github.com/qmu/workaholic --skill translate-qmu
Please help me install this Agent Skill. Skill: translate Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/translate Command: npx skills add https://github.com/qmu/workaholic --skill translate-qmu
Translating English Markdown documents into other languages often leads to formatting drift, broken links, and untranslated technical terms. This Skill ensures translations preserve the original structure, frontmatter semantics, and code integrity.
Translate the English documentation in the repository to the target language using the translate skill. For example, generate ja/README.md and corresponding translations for guidance, guides, and READMEs.
High-intent search queries and answers about installing and using this skill.
To translate Markdown files while preserving frontmatter and code blocks, use this tool to target prose translation and keep code blocks, paths, URLs, and technical terms in English. It translates frontmatter values while keeping keys and structure intact.
The best way to localize English documentation without breaking links is to use a translation process that preserves formatting and enforces parallel translations. This tool maintains consistent link structures and outputs language-specific versions like ja/README.md.
Yes, you can translate frontmatter values without changing the original keys. This tool enforces frontmatter translation by converting only the values while keeping the keys and structural semantics completely intact.
Yes, Markdown translation supports custom output naming patterns like README.ja.md and ja/README.md. These conventions help maintain parallel directory structures and consistent link architecture across multilingual documentation.
Translated Markdown documentation experiences formatting drift and broken links when the translation process alters structural elements. Using a tool that preserves Markdown structure, HTML tags, and URLs ensures the translated output remains consistent with the original.
When localizing technical Markdown documentation, you should keep code blocks, paths, URLs, and technical terms untranslated. This ensures code integrity and prevents broken links while translating the surrounding prose into the target language.
typemdSynchronize Chinese blog posts into English while preserving markdown formatting.
wahidyankfEnforce accessible markdown content quality standards across repository documentation.
qmuGenerate a consistent term registry with frontmatter and change tracking.
unclejobs-aiTranslate content between English and Korean while preserving markdown formatting and code blocks.
