obsidian-sync_skill

This skill enables secure two-way Obsidian synchronization with Clawdbot by running a dedicated sync server and managing access

Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill obsidian-sync

_meta.json280 B
SKILL.md2.9 KB

Overview

This skill runs a secure sync server to synchronize files between a Clawdbot workspace and Obsidian. It enables two-way file synchronization for notes and memory subdirectories, with token-based authentication and path restrictions. Run it locally or expose via a tunnel for remote access.

How this skill works

The server exposes simple HTTP endpoints to list, read, and write markdown files while enforcing allowed subdirectories and blocking path traversal. All requests require an Authorization Bearer token; conflict detection is applied on writes. It is designed to run as a user service (systemd) or behind a secure tunnel like Tailscale.

When to use it

You want two-way sync between an agent workspace and an Obsidian vault
You need a lightweight backend for the OpenClaw Obsidian plugin
You require token-based authenticated file operations on specific subfolders
You prefer running a local service with optional remote exposure via Tailscale
You need auditability and secure, limited file access

Best practices

Set SYNC_TOKEN to a gateway token and keep it secret (OS keychain recommended)
Restrict SYNC_ALLOWED_PATHS to only required subdirectories (e.g., notes,memory)
Bind to localhost and expose via an authenticated tunnel (Tailscale) rather than public ports
Run the server as a user systemd service for automatic restart and cleaner lifecycle
Monitor /sync/status and enable audit logging for change traces

Example use cases

Connect the OpenClaw Obsidian plugin to a local Clawdbot workspace to edit notes from Obsidian and sync back
Host the sync server on a remote machine and expose it with Tailscale serve for multi-device access
Automate backups by listing and reading files from the allowed paths and storing snapshots
Integrate agent-driven note creation: the agent writes new notes into the workspace and Obsidian pulls updates via the plugin

FAQ

Bind the server to localhost and expose it with Tailscale serve or another authenticated tunnel; always use SYNC_TOKEN and avoid opening public ports.

What folders can the plugin access?

Only subdirectories listed in SYNC_ALLOWED_PATHS are accessible. Path traversal is blocked to prevent access outside the workspace.

How are write conflicts handled?

Writes use conflict detection: the server checks metadata and will return a conflict response if concurrent changes are detected, allowing the client to reconcile.