LaunchKit · 2026
Back to Skills

save-to-obsidian

Saves markdown content to remote Obsidian vault via SSH.

1
1.1k downloads
by @chunhualiao

Setup & Installation

openclaw skills install @chunhualiao/save-to-obsidian

Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:

npx clawhub install save-to-obsidian

Version History

v1.1.0Feb 18, 2026 - Version note by skill developer:

v1.1.0: Added save script with error handling, edge cases, trigger coverage, agent owner

What This Skill Does

Saves markdown content to a remote Obsidian vault over SSH using SCP. Built for Linux and Ubuntu machines that lack iCloud sync and cannot write directly to the vault. Enforces Obsidian-compatible formatting: Mermaid diagrams, markdown tables, and wiki-links.

Handles SSH transfer, filename sanitization, and Obsidian-specific formatting in one step, instead of manual SCP commands that risk broken ASCII diagrams or invalid filenames.

When to use it

  • Archiving AI-generated research notes from a Linux server to Obsidian
  • Sending meeting summaries from a remote machine to a personal knowledge base
  • Pushing generated documentation into an Obsidian vault for later review
  • Storing code analysis output in Obsidian without manual file transfer
  • Saving agent outputs to a Mac-hosted vault from a headless server

Example Workflow

Here's how your AI assistant might use this skill in practice.

INPUT

User asks: save this project summary to Obsidian

AGENT
  1. 1Writes content to a temporary .md file with Obsidian-compatible formatting
  2. 2Reads SSH host, user, and vault path from workspace TOOLS.md
  3. 3Copies the file to the remote vault using scp
  4. 4Deletes the temporary file after successful transfer
  5. 5Reports the saved filename and vault path to the user
OUTPUT

File 'project-summary.md' saved to ~/Obsidian/MyVault/ on vault.example.com

Requirements

Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.

Obsidian installed on a remote machine with an existing vaultSSH key-based authentication configured for the remote machine