メニュー
Initialize or safely upgrade a DeepOrbit Obsidian vault. Use when the user asks to set up DeepOrbit, create the vault folders, migrate legacy Chinese folder names, repair a partial installation, or generate deeporbit.json.
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.init |
| description | Initialize or safely upgrade a DeepOrbit Obsidian vault. Use when the user asks to set up DeepOrbit, create the vault folders, migrate legacy Chinese folder names, repair a partial installation, or generate deeporbit.json. |
Run the deterministic initializer from the installed CLI and point it at the DeepOrbit repository checkout that should be materialized into the vault:
deeporbit --vault "<vault-path>" init --source "<deeporbit-repo-path>"
If the deeporbit executable is unavailable, run PYTHONPATH=<repo>/src python -m deeporbit --vault "<vault-path>" init --source "<repo>".
The command is idempotent. It creates missing folders, including 15_Writings, preserves existing notes, merges legacy localized folders only when safe, and reports conflicting files without overwriting either copy.
Initialization materializes the workflow skills into 99_System/DeepOrbit/skills/, writes 99_System/DeepOrbit/skills-index.json, overlays missing system templates/prompts/Bases, refreshes mentor guides, and copies a curated runtime bundle into 99_System/DeepOrbit/repo/. The bundle is the project-level handoff surface: it includes skills, commands, prompts, hooks, CLI source, MCP, docs, and manifests, but excludes .git, virtualenvs, caches, build outputs, node_modules, and generated agent install directories.
External workspaces should install only the global do.link connector; after init, the vault itself carries the workflow catalog needed for routing.
After initialization:
conflicts is non-empty, show every path and ask the user how to merge it; do not delete either file.deeporbit --vault "<vault-path>" doctor.