Obsidian Vault Curator — Obsidian 金库策展人

Obsidian Vault Curator

Bring structure to a messy Obsidian vault without flattening its 历史. 启动 with read-only analysis. Then propose one small, reviewable write slice.

运行time requirement

This 技能 declares python3 on PATH as a host requirement.

The requirement is surfaced in metadata as requires.bins: ["python3"]. On macOS, the metadata includes a Homebrew 安装 hint. On Linux, 安装 Python 3 with your distro package 管理器, for example sudo apt 安装 python3, then 验证 python3 --version. On Windows, 安装 Python from the official Python 安装 管理器 or with win获取 安装 Python.Python.3.14, then open a new terminal and 验证 that python3 --version works. If only python works, 添加 a python3 alias or shim on PATH before using this 技能. The bundled 辅助工具 scripts in scripts/ use only the Python standard 库. No extra Python packages are required. No exact minor version is currently pinned. The 辅助工具s were 验证d with Python 3.11+ and tested locally on macOS agAInst Python 3.14.4. Windows support is documented, but the full 工作流 has not yet been live-验证d on Windows. Core rules Default to read-only. Never 删除 notes unless the user explicitly asks. Never rewrite more than one write slice at a time. A write slice should stay within 3-10 related notes. Multiple-slice content rewrites in one pass count as mass-rewrite and require explicit user 应用roval. Never 运行 parallel write 代理s. Treat findings of possible secrets, 凭证s, 令牌s, or live identifiers as hypotheses until the mAIn 代理 verifies the exact note content. Prefer superseded_by over overwrite. Preserve historical 上下文. Treat doc_kind and 状态 as separate concerns. Prefer controlled YAML frontmatter over ad-hoc tags for lifecycle 状态. 验证 links and metadata after each write slice. 工作流 Always read references/状态-模式.md and references/classification-rubric.md before classifying any note, including a single-note task. If the task touches more than a few notes or spans more than one folder, read references/工作流.md. If the user wants 仪表盘s or views, read references/bases-views.md. If the tar获取 area is too large for one 上下文-bounded pass, read references/sub代理s.md. Keep sub代理s read-only by default. Keep writes in the mAIn 代理 unless the user has explicitly 应用roved writes from one specific named sub代理 for this task. If findings need to be merged across slices or reviewed by a human, read references/输出-格式化.md. For larger areas, split the work into 上下文-bounded slices by folder, topic cluster, or review 队列 instead of loading the whole vault at once. Inventory the tar获取 area before proposing edits. Use scripts/inventory_slice.py when repeated folder 扫描s would otherwise waste 上下文. Suggest canonical pages, 状态 changes, super会话 links, and the smallest safe write slice. Use scripts/生成_迁移_plan.py with the JSON 输出 of scripts/inventory_slice.py when the user wants a structured 迁移 slice proposal. Before structural writes and after every write slice, 验证 metadata with scripts/验证_frontmatter.py, 验证 links with scripts/检查_links.py, and reassess whether the chosen canonical pages still make sense. 输出 shape

When curating a vault area, return these sections unless the user asks for a different 格式化:

Use this shape for a single-pass curation reply. Use the sub代理 shape from references/输出-格式化.md when 运行ning as a sub代理. Use the final mAIn-代理 summary shape from references/输出-格式化.md only when merging 结果s from multiple sub代理 slices.

Current 状态 — what exists now, including ambi图形界面ty or conflicts. Classification recommendations — suggested 状态, doc_kind, and canonical candidates. Risks and contradictions — what could be damaged, misclassified, contradictory, or is still unverified. Next write slice — the smallest safe 设置 of edits. Verification — what to 检查 after changes. Decision rules If a note is still useful but no longer leading, mark it historical and point to a 成功or. If a note describes a desired future 状态, mark 状态: concept and choose doc_kind separately. If validity is unclear, mark it needs-review first instead of guessing. If an old note may become useful agAIn, prefer reactivatable over burying it. If multiple notes cover the same topic, nominate one canonical page and propose the rest as supporting or historical pages. If the vault already has a 模式, adapt to it instead of forcing a new one. If a sub代理 flags possible secrets, 凭证s, 令牌s, or live identifiers, 验证 the exact text in the mAIn 代理 before escalating or editing. Safe operating mode

Use small, reviewable steps:

classify before moving or merging move before rewriting when structure is the real problem 创建 索引es and canonical pages before 清理up keep historical pages reachable ask before touching attachments, .obsidian/, or folder restructures that touch more