Run any Skill in Manus with one click

obsidian-sync-doctor

Stars26

Forks5

UpdatedJune 21, 2026 at 09:30

Diagnose the Hermes Agent to Obsidian Sync loop on a VPS, including obsidian-headless, systemd service status, vault path mismatches, login or subscription issues, and two-way sync tests. Use when notes are not appearing on Mac, Telegram captures fail, or the video setup needs proof before recording.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

david-internal

david-internal/hermes-obsidian-giveaway-pack

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

File Explorer

4 files

SKILL.md

readonly

name	obsidian-sync-doctor
description	Diagnose the Hermes Agent to Obsidian Sync loop on a VPS, including obsidian-headless, systemd service status, vault path mismatches, login or subscription issues, and two-way sync tests. Use when notes are not appearing on Mac, Telegram captures fail, or the video setup needs proof before recording.

Obsidian Sync Doctor

Overview

Diagnose the full loop: Hermes writes to the VPS vault folder, obsidian-headless syncs it, and Obsidian on the Mac receives it. Prefer concrete filesystem and service checks over vague advice.

Diagnostic Order

Confirm the expected vault path.
Confirm OBSIDIAN_VAULT_PATH points to that exact path.
Confirm ob is installed and authenticated.
Confirm the vault folder is the folder configured by ob sync-setup.
Confirm obsidian-sync.service is active and enabled.
Inspect recent logs.
Run a one-off sync.
Optionally create a test note and sync it.
Ask the user to confirm the note appears on the Mac.
Ask the user to create a Mac note and confirm it appears on the VPS.

Quick Command

Read-only check:

bash scripts/verify_hermes_obsidian_loop.sh --vault /root/HermesVault

Write a test note and run sync:

bash scripts/verify_hermes_obsidian_loop.sh --vault /root/HermesVault --write-test

Common Diagnoses

Notes created but not synced: service down, bad auth, wrong vault path, or wrong remote vault.
Service active but no Mac note: Mac is on a different account or remote vault.
ob missing: npm global bin is not on PATH, or obsidian-headless was not installed.
Login failures: often inactive Obsidian Sync or wrong account.
Vault at /root: setup was run from the wrong directory.

Resources

Read references/diagnostic-playbook.md for the full decision tree.
Run scripts/verify_hermes_obsidian_loop.sh on the VPS.

Completion Criteria

Finish only when the cause is identified or the user has a concrete next check, and the two-way sync test has either passed or failed with a specific reason.

More from this repository

same repository

hermes-obsidian-setup

david-internal/hermes-obsidian-giveaway-pack

Guide a user or agent through setting up Hermes Agent on a VPS with Obsidian Sync, obsidian-headless, a systemd continuous sync service, Telegram capture, and OBSIDIAN_VAULT_PATH. Use when someone wants the always-on Hermes and Obsidian setup from the video, needs copy-paste VPS commands, or needs to avoid sync gotchas.

2026-06-2126

obsidian-vault-curator

david-internal/hermes-obsidian-giveaway-pack

Organize raw captures, PDFs, links, meeting notes, Telegram dumps, and project notes into an Obsidian vault using Markdown, wikilinks, tags, source notes, maps of content, and inbox triage. Use when an agent needs to maintain a self-organizing second brain rather than control the Obsidian app.

2026-06-2126

telegram-to-obsidian-capture

david-internal/hermes-obsidian-giveaway-pack

Convert messy Telegram messages, voice transcriptions, URLs, PDFs, screenshots, and pasted conversations into Obsidian-ready notes with titles, summaries, source trails, tasks, wikilinks, and tags. Use when the Hermes and Telegram workflow receives raw captures for the vault.

2026-06-2126

name	obsidian-sync-doctor
description	Diagnose the Hermes Agent to Obsidian Sync loop on a VPS, including obsidian-headless, systemd service status, vault path mismatches, login or subscription issues, and two-way sync tests. Use when notes are not appearing on Mac, Telegram captures fail, or the video setup needs proof before recording.

Obsidian Sync Doctor

Overview

Diagnose the full loop: Hermes writes to the VPS vault folder, obsidian-headless syncs it, and Obsidian on the Mac receives it. Prefer concrete filesystem and service checks over vague advice.

Diagnostic Order

Confirm the expected vault path.
Confirm OBSIDIAN_VAULT_PATH points to that exact path.
Confirm ob is installed and authenticated.
Confirm the vault folder is the folder configured by ob sync-setup.
Confirm obsidian-sync.service is active and enabled.
Inspect recent logs.
Run a one-off sync.
Optionally create a test note and sync it.
Ask the user to confirm the note appears on the Mac.
Ask the user to create a Mac note and confirm it appears on the VPS.

Quick Command

Read-only check:

bash scripts/verify_hermes_obsidian_loop.sh --vault /root/HermesVault

Write a test note and run sync:

bash scripts/verify_hermes_obsidian_loop.sh --vault /root/HermesVault --write-test

Common Diagnoses

Notes created but not synced: service down, bad auth, wrong vault path, or wrong remote vault.
Service active but no Mac note: Mac is on a different account or remote vault.
ob missing: npm global bin is not on PATH, or obsidian-headless was not installed.
Login failures: often inactive Obsidian Sync or wrong account.
Vault at /root: setup was run from the wrong directory.

Resources

Read references/diagnostic-playbook.md for the full decision tree.
Run scripts/verify_hermes_obsidian_loop.sh on the VPS.

Completion Criteria

Finish only when the cause is identified or the user has a concrete next check, and the two-way sync test has either passed or failed with a specific reason.