菜单
Use when reading or writing files in an Obsidian vault that is synced with obsync. Ensures changes are pulled before reading and pushed after writing. Also covers sync status, file history, version restore, and diagnosing sync issues.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/obra/dotfiles --skill syncing-obsidian命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Use when the user asks to fix open failing reviews, invokes /roborev-fix, or provides job IDs; do not use when the user only pastes review findings with no request to discover or close reviews
Allows you to view the user's screen as well as several hours of history. Use when the user makes a reference to their recent work, for which it'd be helpful to see the screen. This skill MUST be used whenever you need to resolve ambiguity in a user request, where the user hasn't specified enough context to do the task. Examples include disambiguating the specific user/app/document/error the user is referring to. You must also use this skill if the user asks about any question regarding Chronicle or asks what you can see from the screen.
Use when the user asks to fix open failing reviews, invokes $roborev-fix, or provides job IDs; do not use when the user only pastes review findings with no request to discover or close reviews
| name | syncing-obsidian |
| description | Use when reading or writing files in an Obsidian vault that is synced with obsync. Ensures changes are pulled before reading and pushed after writing. Also covers sync status, file history, version restore, and diagnosing sync issues. |
Sync Obsidian vaults from the command line using the obsync CLI. Works with Obsidian Sync servers alongside official Obsidian clients.
If obsync watch is running, the vault is kept in sync automatically — no manual sync is needed before reading or after writing.
If watch mode is not running, always sync manually:
Before reading vault files, pull the latest from the server:
obsync sync /path/to/vault
After writing or modifying vault files, push your changes:
obsync sync /path/to/vault
If you skip these steps and watch is not running, you will read stale content or your changes will not reach other devices.
obsync sync does both pull and push in one call, so it is safe to use in both cases.
Use this skill when:
# Log in
obsync login
# List available vaults
obsync vaults
# Initialize a vault in a directory
obsync init <vault-id> /path/to/vault
After init, all commands run from within the vault directory (or pass the directory as the last argument).
obsync sync [directory]
Pulls remote changes, resolves conflicts, then pushes local changes. If directory is omitted, uses the current working directory.
obsync pull [directory] # download remote changes only
obsync push [directory] # upload local changes only
obsync watch [directory]
Keeps the WebSocket connection open, pulls remote changes in real-time via push notifications, and scans for local changes every 30 seconds. Reconnects automatically on connection loss. Stop with Ctrl+C.
Only one obsync process can run per vault (file lock in .obsync/obsync.lock). If watch is running, obsync sync will fail with a lock error — this is expected since watch handles syncing.
obsync status [directory]
Shows vault info, file counts, and any files that have changed since last sync.
obsync history "path/to/file.md" [directory]
Shows all versions with UID, timestamp, device, and size. Use the UID to restore.
obsync restore "path/to/file.md" <version-uid> [directory]
obsync diag [directory]
Tests connectivity, push/echo round-trip, vault size, and deleted file count.
Add --debug before any command to see WebSocket messages and protocol details on stderr:
obsync --debug sync
Every sync appends to .obsync/sync.log inside the vault:
2026-02-02 14:47:25 sync started
2026-02-02 14:47:26 pull "meeting.md" downloaded from server
2026-02-02 14:47:26 pull "draft.md" deleted (server deleted)
2026-02-02 14:47:26 pull "notes.md" kept local version
2026-02-02 14:47:26 push "new-note.md" uploaded (1234 bytes)
2026-02-02 14:47:26 push "old-note.md" server has current version
2026-02-02 14:47:26 sync complete
Log entry meanings:
downloaded from server — server version was newer, wrote to diskdeleted (server deleted) — file was deleted on another device, removed locallykept local version — local edits preserved over server changesmerged (text) — both sides changed a markdown file, three-way merge appliedmerged (json) — both sides changed a config JSON, shallow merge applieduploaded (N bytes) — file pushed to serverserver has current version — server already had this version, no upload neededobsync status
If the file doesn't appear as changed, it's already marked as synced. Run obsync push and check the activity log.
Run obsync sync and check .obsync/sync.log. If the file doesn't appear, the server hasn't sent a notification for it. Try obsync --debug sync and look for push notifications mentioning the file.
Deletions require the initial flag to be cleared. Run obsync sync once to clear it, then deletions from other devices will be processed on subsequent syncs.
The sync state lives in .obsync/state.db (SQLite):
# Files that need pushing (changed locally since last sync)
sqlite3 .obsync/state.db "SELECT path FROM local_files WHERE hash != synchash"
# Server-side deleted files
sqlite3 .obsync/state.db "SELECT path FROM server_files WHERE deleted = 1"
# Current sync metadata
sqlite3 .obsync/state.db "SELECT * FROM metadata"
Reset its sync state so it appears as changed:
sqlite3 .obsync/state.db "UPDATE local_files SET synchash='' WHERE path='path/to/file.md'"
obsync push
Roll back the version cursor to re-receive push notifications:
# Check current version
sqlite3 .obsync/state.db "SELECT value FROM metadata WHERE key='last_version'"
# Roll back (e.g., by 10 versions)
sqlite3 .obsync/state.db "UPDATE metadata SET value='7040' WHERE key='last_version'"
obsync sync
.git/, .obsidian/, .obsync/)workspace.json and workspace-mobile.jsonNote: .obsidian/ config files are synced by the server (they arrive as push notifications) even though the local scanner skips dotfolders.
When both local and remote changed the same file:
| File type | Resolution |
|---|---|
Markdown (.md) | Three-way merge using common ancestor |
JSON in .obsidian/ | Shallow merge (server keys win, local-only keys kept) |
| Everything else | Local version wins |
A backup is saved before any merge.