AI Agent Hub
Back to skills
Claw Memo Obsidian Sync icon

Claw Memo Obsidian Sync

Knowledge Management Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md and install @user_5bab6d4d/claw-memo-obsidian.

About this skill

Problem

Agent configs often sit across workspaces. Core files include AGENTS.md, IDENTITY.md, MEMORY.md, SOUL.md, and USER.md, covering workflow, identity, memory, persona, and user preferences. Manually copying them into Obsidian is easy to botch: files are missed, formatting breaks, and there is no date-based trail. claw-memo-obsidian handles this repetitive archive step by syncing a selected agent’s core configs into a Vault and preserving them in date folders.

How It Works

The skill first parses dates, file names, and a Vault path from natural language, then checks that the target directory is writable. It creates a date folder, maps source files to 01-AGENTS.md through 05-USER.md, and adds YAML Frontmatter with metadata such as type and tags. For multi-agent setups, it derives the sync folder from the workspace name or config, for example ai-write maps to ai_write_memo, reducing the chance of writing into the wrong agent folder.

Limits And Notes

It is best for one-way backups and periodic archiving, not bidirectional sync; the default list covers five core files. Deleting directories requires confirmation, and existing files may prompt for overwrite or create a backup version. Keep the Vault path present and writable, and use UTF-8 to avoid Chinese mojibake.

Use Cases

  • Maintain an OpenClaw workspace by backing up core files like `AGENTS.md` and `MEMORY.md` into dated Obsidian folders.
  • Use Claude Code, Codex, and OpenClaw together, then archive each workspace’s configs into separate folders.
  • Organize Obsidian notes by automatically adding `Frontmatter`, `type`, and `tags` to synced files.
  • Check agent configs against the knowledge base periodically and confirm whether to overwrite existing files.

Best For

  • Agent engineers maintaining OpenClaw workspaces who need dated Obsidian archives of core configs.
  • Automation developers running multiple agent workspaces who need to avoid writing backups into the wrong folder.
  • Engineers managing Obsidian vaults who need structured `Frontmatter` on synced notes.
  • Independent developers auditing agent memory and user configs who want searchable historical versions.