How do I install the Do.translate Markdown skill?

Run npx skillmds@latest add dull-bird/do-translate-markdown in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Do.translate Markdown safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Do.translate Markdown?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Do.translate Markdown free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Do.translate Markdown?

dull-bird (@dull-bird) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Do.translate Markdown by dull-bird — Agent Skill

Name: Do.translate Markdown
Author: dull-bird

Do.translate Markdown

Translate Markdown documents to a target language with checkpointed completeness, glossary consistency, and structural verification. Use when the user asks to translate Markdown, notes, documentation, or long structured text while preserving code, links, math, wikilinks, and formatting.

dull-bird acfc157 2.5 KB Updated Sep 17, 2026

File contents

Translate Markdown

Write a new output file; never overwrite the source. Preserve code, math, URLs, wikilink targets, and Markdown structure.

1. Set language and inspect the source

Use the user's explicit target language. Otherwise read deeporbit.json and confirm the configured language. Read the full source before translating.

Create <name>_translation_manifest.md:

---
deeporbit_workflow: 1
workflow_id: translate-<date>-<slug>
status: active
source: <name>.md
output: <name>_<LANG>.md
---

# Terminology Glossary
| Source | Translation | Notes |
|---|---|---|

# Section Checklist
- [ ] Frontmatter and title
- [ ] Section 1
- [ ] Section 2
- [ ] Footnotes and references

Capture recurring terminology, proper nouns, and intentional untranslated terms before translating prose.

2. Translate with checkpoints

For each unchecked section:

Reread the glossary and relevant source context.
Translate into natural target-language prose.
Preserve heading levels, paragraph count, list nesting, tables, callout types, link destinations, code, and math.
In Mermaid blocks, translate labels only; preserve IDs and syntax.
Compare source and output section structure.
Mark the section checked only after verification.

Continue while context allows. If interrupted, resume from the first unchecked item. Runtime Goals and Trackers may mirror the objective but never replace the manifest. Do not use an external self-invoking loop.

3. Final verification

Every source paragraph has an output counterpart.
Heading hierarchy and list structure match.
Glossary terms are consistent.
Code blocks, formulas, URLs, and wikilink targets are unchanged.
No new claims or explanations were introduced.
Set author: ai in frontmatter for every note you create; switch to author: mixed when substantially rewriting a human-authored note. Authorship lives in frontmatter only — never add visible badges. Write output as <name>_<LANG>.md with translated title, source wikilink, language, translation date, and translation tag. Keep the manifest for audit unless the user requests cleanup. Open the output through do.obsidian-open; opening failure is non-fatal.

---name: do-translate-markdowndescription: Translate Markdown documents to a target language with checkpointed completeness, glossary consistency, and structural verification. Use when the user asks to translate Markdown, notes, documentation, or long structured text while preserving code, links, math, wikilinks, and formatting.---# Translate MarkdownWrite a new output file; never overwrite the source. Preserve code, math, URLs, wikilink targets, and Markdown structure.## 1. Set language and inspect the sourceUse the user's explicit target language. Otherwise read `deeporbit.json` and confirm the configured language. Read the full source before translating.Create `<name>_translation_manifest.md`:```markdown---deeporbit_workflow: 1workflow_id: translate-<date>-<slug>status: activesource: <name>.mdoutput: <name>_<LANG>.md---# Terminology Glossary| Source | Translation | Notes ||---|---|---|# Section Checklist- [ ] Frontmatter and title- [ ] Section 1- [ ] Section 2- [ ] Footnotes and references```Capture recurring terminology, proper nouns, and intentional untranslated terms before translating prose.## 2. Translate with checkpointsFor each unchecked section:1. Reread the glossary and relevant source context.2. Translate into natural target-language prose.3. Preserve heading levels, paragraph count, list nesting, tables, callout types, link destinations, code, and math.4. In Mermaid blocks, translate labels only; preserve IDs and syntax.5. Compare source and output section structure.6. Mark the section checked only after verification.Continue while context allows. If interrupted, resume from the first unchecked item. Runtime Goals and Trackers may mirror the objective but never replace the manifest. Do not use an external self-invoking loop.## 3. Final verification- Every source paragraph has an output counterpart.- Heading hierarchy and list structure match.- Glossary terms are consistent.- Code blocks, formulas, URLs, and wikilink targets are unchanged.- No new claims or explanations were introduced.- Set `author: ai` in frontmatter for every note you create; switch to `author: mixed` when substantially rewriting a human-authored note. Authorship lives in frontmatter only — never add visible badges.Write output as `<name>_<LANG>.md` with translated title, source wikilink, language, translation date, and `translation` tag. Keep the manifest for audit unless the user requests cleanup. Open the output through `do.obsidian-open`; opening failure is non-fatal.

Frequently asked questions