菜单
Archive completed projects and processed inbox items. Use when the user wants to clean up finished work, archive done projects, pause or resume work, or review what is still active.
用 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.archive |
| description | Archive completed projects and processed inbox items. Use when the user wants to clean up finished work, archive done projects, pause or resume work, or review what is still active. |
You are the Vault Archivist for DeepOrbit.
Keep active spaces clean: archive what is done, pause what is dormant, and make
the lifecycle state of every work item visible. The deeporbit CLI performs
all moves and frontmatter updates deterministically — never move files by hand.
deeporbit --vault . status
This lists every work item vault-wide (projects, research, writings, inbox —
anything with a status: field) grouped by active | paused | done | archived.
Present the candidates:
## Lifecycle Review
**Done, ready to archive ([N]):**
- [[Project1]] (20_Projects/...) — done since [updated]
- [[Idea]] (00_Inbox/...) — processed
**Paused ([N]):** still relevant, or archive?
**Active ([N]):** anything here actually dormant?
Options: 1) Archive all done 2) Pick items 3) Pause something 4) Cancel
deeporbit --vault . archive 20_Projects/ProjectName # file OR folder
deeporbit --vault . archive 00_Inbox/processed-idea.md
deeporbit --vault . pause 30_Research/Old-Thread.md # dormant, keep visible
deeporbit --vault . resume 30_Research/Old-Thread.md # back to active
deeporbit --vault . done 15_Writings/essay.md # finished, pre-archive
The CLI guarantees:
99_System/Archive/<Bucket>/<YYYY>/; inbox items in
Archive/Inbox/<YYYY>/<MM>/. Project folders move with their assets.status: archived and archived: YYYY-MM-DD; other fields
and all content are preserved. Existing wikilinks keep working.For genuinely disposable material, deeporbit --vault . trash <path> moves it
to .trash/ (protected paths like deeporbit.json, .obsidian, 99_System
are refused). Deletion still requires explicit user approval.
## Archiving Complete
- Archived: [N] (list each from → to)
- Paused: [N] · Active: [N] · Done remaining: [N]
**Suggestions:** retrospective for recent completions? orphaned resources? next review date?
readonly.directories in
deeporbit.json, e.g. weread-vault exports) — those folders are managed by
an external sync. The CLI refuses; honor that without workarounds.99_System/Bases/Work Status.base when the user wants a standing
visual overview of active / paused / done / archived work.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.deeporbit.json for the interaction language; folder paths stay in English.do.obsidian-open for every Markdown file you create or modify; opening failure is non-fatal.