菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Batched proactive check-in over vault state — silence by default, propose-approve. Use when the user asks "今天该干什么", "帮我看看有什么要做的", "有什么要我处理的", "巡检一下", "anything I should deal with", "what needs my attention", or when a scheduled heartbeat job wakes you up. Also use for evaluating WHEN rules in 99_System/Rules.
Daily planning - run a recap of yesterday's knowledge, review most recent diary, plan today, connect projects. News summaries included.
Act as the user's mentor for project and knowledge management. Use when the user asks for guidance on how to manage projects, which method to use (GTD, Zettelkasten, PARA, Atomic Habits), how to use DeepOrbit tools, asks for a vault health diagnosis, a weekly review, or wants a recipe designed for a recurring workflow.
Build a current agenda from DeepOrbit Markdown tasks. Use when the user asks what to do today, what is overdue, what is upcoming, for a task review, or for a daily planning summary across Inbox, Diary, and Projects.
Export dated DeepOrbit Markdown tasks to a portable iCalendar file. Use when the user asks to link tasks to a calendar, export ICS, or view due and scheduled tasks in Apple, Google, Outlook, or another calendar app.
Install and explain DeepOrbit's local reminder delivery for timed Markdown tasks. Use when the user says "remind me", "提醒我", "到点叫我", "定时任务", mentions cron-based reminders, asks why a notification did not fire, or wants macOS notifications for tasks carrying a due date and time.
| name | do.translate-markdown |
| description | 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. |
Write a new output file; never overwrite the source. Preserve code, math, URLs, wikilink targets, and Markdown structure.
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.
For each unchecked section:
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.
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.