obsidian-sync

What This Skill Does

The obsidian-sync skill acts as a secure, high-performance bridge between your local Obsidian vault and your Clawdbot agent. By hosting a lightweight Node.js synchronization server, this skill allows your agent to read, write, and manage markdown files directly within your notes directory. It facilitates true two-way synchronization, ensuring that any edits made by the AI agent are reflected in your vault, and your personal changes remain accessible to the agent for context-aware interactions.

Installation

To begin, ensure you have Node.js installed on your system. First, clone or download the skill from the obsidian-openclaw repository. Install dependencies, then generate your gateway token to secure the endpoint. You can run the server manually using SYNC_TOKEN="your-token" node scripts/sync-server.mjs, or deploy it as a persistent systemd service on Linux to ensure the server starts automatically on boot. For external access, it is recommended to use Tailscale serve to expose the local port 18790 securely over your own private network mesh.

Use Cases

This skill is perfect for users who want to turn their Obsidian vault into a living knowledge base. Common use cases include: utilizing the agent to organize complex research notes, drafting daily journal entries through natural language prompts, or performing bulk refactoring of markdown files. It serves developers who want to keep project documentation synced with their AI assistant, and writers who use the agent as an editor to clean up and structure long-form content.

Example Prompts

1. "Sync my latest notes from the 'Projects' folder and summarize the key action items from today's meeting."
2. "Create a new markdown note in the 'Daily' directory titled 'Brainstorming' and add the following bullet points regarding the new marketing strategy."
3. "Compare the contents of my memory file with my current research notes and consolidate any overlapping information into a single master summary."

Tips & Limitations

For security, the skill strictly limits file operations to authorized subdirectories such as 'notes' and 'memory'. Always ensure your SYNC_TOKEN is kept private, as it grants full read/write access to the configured directories. While the server blocks path traversal attempts to prevent unauthorized file access, it is best practice to keep your sync server off the public internet. If you encounter sync conflicts, verify that the Obsidian plugin is updated to the latest version to leverage built-in conflict detection.