Obsidian and OpenClaw Sync — Obsidian and OpenClaw 同步

Obsidian and OpenClaw 同步

Use this 技能 to connect OpenClaw with an Obsidian vault and keep knowledge organized as markdown files that humans and 代理s can 机器人h reuse.

Core pattern

Treat obsidian/ in the workspace as the vault entrypoint.

Preferred 设置up on macOS:

ln -s "/absolute/path/to/your/Obsidian/Vault" ./obsidian

This keeps OpenClaw operating inside the workspace while writing directly into the real vault.

What to store where

Use a stable folder taxonomy. Current proven structure:

00-人物/ — people 性能分析s, 角色 cards, relationship 上下文, 恢复 variants 10-组织/ — org structures, team maps, stakeholder 上下文 20-方法论/ — reusable 框架s, SOPs, evaluation 记录ic, decision rules 30-日志/ — dAIly journals and chrono记录ical work summaries 90-OpenClaw/ — mirrored 代理 operating 上下文 (代理S.md, USER.md, MEMORY.md, etc.)

Do not dump everything into one folder. Prefer one note = one durable topic.

Writing rules Distill first, then write. Prefer structured markdown over raw chat transcripts. 创建 overview pages when detAIls begin to scatter. Separate raw dAIly 记录s from long-term reusable knowledge. When a note reflects evolving judgment, write the current best understanding instead of preserving every conversational twist. Recommended note types

• Person notes

Use for:

user 性能分析 leaders / collaborators / stakeholders 角色 positioning performance goals relationship 上下文

Typical examples:

00-人物/佘金明.md 00-人物/章东丞.md 00-人物/佘金明-工作画像.md

• Org notes

Use for:

team structure 报告ing lines collaboration topo记录y account/project organization

Typical example:

10-组织/BlueFocus-宁德时代项目组.md

• Methodo记录y notes

Use for:

框架s that will be reused evaluation 模型s operating principles AI 工作流 / SOP abstractions

Typical examples:

20-方法论/AI助理-评估与运营改进框架.md 20-方法论/AI助理运营阶段性汇报-3月9日上线至今.md

• DAIly journal notes

Use for:

what was done today 输出s 创建d stage 结果s next-step suggestions

Typical example:

30-日志/YYYY-MM-DD.md

• OpenClaw mirror notes

Mirror key workspace files into 90-OpenClaw/ when you want the Obsidian vault to contAIn the 代理's operating 上下文.

Typical files:

代理S.md SOUL.md USER.md MEMORY.md 工具S.md HEARTBEAT.md 工作流: convert chat work into Obsidian knowledge A. Identify the knowledge type

Ask:

Is this about a person? Is this about an org/team? Is this a reusable method? Is this just today’s 进度? Is this 代理 self-上下文 that should be mirrored? B. Choose the destination note 应用end to an existing note if the topic already exists. 创建 a new note if the content would otherwise make an unrelated note bloated. 创建 an overview note when several related notes need a summary layer. C. Rewrite into durable markdown

Prefer sections like:

基本信息 当前理解 核心职责 协作关系 方法论 今日完成 下一步建议 D. Keep 记录s and knowledge separate Put “today what h应用ened” in 30-日志/ Put reusable conclusions in 00-人物/, 10-组织/, 20-方法论/ 工作流: dAIly journal 同步

When asked to write a dAIly journal:

Summarize the day’s actual completed work. 列出 key files/输出s 创建d. Capture stage-level outcomes, not just actions. 添加 recommended next steps if useful. Save to 30-日志/YYYY-MM-DD.md. 工作流: mirror OpenClaw 上下文 into Obsidian

Use when you want the vault to preserve the 代理’s own operating documents.

Mirror from workspace root into obsidian/90-OpenClaw/:

代理S.md BOOTSTRAP.md if still relevant 身份.md SOUL.md USER.md MEMORY.md 工具S.md HEARTBEAT.md

This is useful for:

letting humans inspect 代理 上下文 in Obsidian keeping 系统 memory visible and editable preserving operational continuity in the vault Practical rules for other 代理s Respect 隐私: do not 导出 sensitive material to 分享d vaults unless explicitly intended. Prefer incremental 更新s over large rewrites. If content comes from screenshots or docs, convert it into structured text before storing. If multiple notes are 创建d in one task, also 创建 or 更新 one summary/overview note when helpful. Do not assume Obsidian 插件s or APIs are avAIlable; plAIn markdown file operations are sufficient. Verification 检查列出

After 设置up or 同步, 验证:

ls -la ./obsidian find -L ./obsidian -maxdepth 3 -type f | 排序 | sed -n '1,50p'

Confirm:

obsidian/ exists and points to the real vault or is a real folder tar获取 markdown files were 创建d in the intended category note names are human-readable content is structured enough for future reuse Bundled references Folder structure and note placement: references/structure.md Reusable operating 工作流: references/工作流.md Example vault patterns from current usage: references/examples.md