save-to-obsidian

# Save to Obsidian

Saves markdown content to remote Obsidian vault via SSH.

## Prerequisite

**This skill is for machines WITHOUT iCloud sync** (e.g., Linux/Ubuntu servers). If your machine already has iCloud Desktop sync enabled and direct access to the Obsidian vault, you don't need this skill — just copy files directly to the vault path.

## When to Use

User says: "save to obsidian", "send to obsidian", "copy to obsidian"

## Process

1. Write content to a temp .md file (enforce formatting rules below)
2. Copy to remote vault: `scp <filepath> user@remote-host:/path/to/obsidian/vault/`
3. Confirm success to user

**Example:**
```bash
# Write content to temp file
cat > /tmp/my-note.md << 'EOF'
# My Note
Content here
EOF

# Copy to remote Obsidian vault
scp /tmp/my-note.md myuser@vault.example.com:~/Obsidian/MyVault/

# Clean up
rm /tmp/my-note.md
```

**Configuration:** The agent should use the SSH host and vault path configured in workspace TOOLS.md

## Formatting Rules

All content saved to Obsidian MUST follow these rules:

### Diagrams: Use Mermaid (mandatory)
- **Never** use ASCII box diagrams, ASCII art, or plaintext diagrams
- **Always** use Mermaid fenced code blocks (` ```mermaid `)
- Obsidian renders Mermaid natively — ASCII diagrams look broken
- Supported types: flowchart, sequence, state, class, ER, gantt, pie, mindmap, timeline, quadrant, graph

### Tables: Use Markdown tables
- Obsidian renders markdown tables natively
- For complex data, prefer tables over bullet lists

### Links: Use wiki-links or relative links
- Link between Obsidian notes: `[[note-name]]`
- External links: standard markdown `[text](url)`

### General
- Use headers (##) for structure — Obsidian outline panel relies on them
- Use YAML frontmatter if metadata is needed
- Keep filenames kebab-case (no spaces) for cross-platform compatibility

## Agent Owner
This skill is executed by the main OpenClaw agent session. The `save-to-obsidian.sh` script
runs as a shell command via the...

# Save to Obsidian

An OpenClaw skill that saves markdown content to an Obsidian vault via SSH, with automatic formatting rules for diagrams, tables, and links.

## Prerequisite

**This skill is for machines WITHOUT iCloud sync** (e.g., Linux/Ubuntu servers, remote machines). If your machine already has iCloud Desktop sync enabled and direct access to the Obsidian vault folder, you don't need this skill — just copy files directly to the vault path.

## What It Does

This skill allows your OpenClaw agent to save any generated markdown content directly to your Obsidian vault on a remote machine. It automatically enforces formatting rules to ensure content renders properly in Obsidian:
- Converts or enforces Mermaid diagrams (no ASCII art)
- Uses markdown tables (Obsidian native rendering)
- Applies kebab-case filenames for cross-platform compatibility

## How to Install

1. Copy this skill to your OpenClaw skills directory
2. Set up SSH access to the remote machine hosting your Obsidian vault
3. Create a script at `~/.openclaw/scripts/save-to-obsidian.sh` that copies files to your vault location
4. Ensure the script is executable and works with your SSH key

Example script:
```bash
#!/bin/bash
scp "$1" user@remote-host:/path/to/obsidian-vault/
```

## Usage

Say to your agent:
- "save to obsidian"
- "send to obsidian"  
- "copy to obsidian"

The agent will format the content appropriately and transfer it to your vault.

## Requirements

- SSH access to the remote machine hosting the Obsidian vault
- Obsidian vault accessible on the remote machine
- A save-to-obsidian.sh script configured for your setup
- **Note:** Not needed if your local machine already has iCloud sync to the vault

## Future Work

- Support for multiple vault destinations
- Direct iCloud sync without SSH intermediary
- Automatic tagging and frontmatter generation
- Batch save operations

## License

MIT