⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
obsidian-desktop-cli
Search, read, create, and manage notes, tasks, and properties in an Obsidian vault using the Obsidian Desktop CLI
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
OpenClaw Desktop
Run OpenClaw and Obsidian together in a Docker container so your AI agent can interact with your Obsidian vault using the Obsidian CLI.
The Obsidian CLI requires the full Obsidian Desktop app to be running (it communicates via IPC), so this project packages everything inside a lightweight XFCE desktop accessible through your browser. Your agent gets shell access to the Obsidian CLI for searching, reading, writing, managing tasks, and more -- all without reading or writing markdown files directly.
Prerequisites
- Docker and Docker Compose
- An Obsidian account with Sync (for pulling your vault into the container)
Security note: The OpenClaw gateway is configured to bind to all network interfaces (LAN mode) so you can access the web UI from other machines on your network. This means anyone on your local network can reach the gateway. Token authentication is enabled by default, but this setup is designed for use on a trusted home network -- not a public or shared network.
Getting Started
You'll be doing three main things to get this up and running:
- Buiding the image and getting the container running.
- Configuring Obsidian and Obsidian Sync within the container.
- Configuring OpenClaw within the container.
Running the Container
-
Clone the repo:
git clone [email protected]:guyroyse/openclaw-obsidian-desktop.git cd openclaw-obsidian-desktop -
Create your
.envfile:cp .env.sample .envEdit
.envand set at leastPASSWORD. See.env.samplefor all available options. -
Build and start the container:
docker compose up -d -
Open the virtual desktop in your browser:
You can use either localhost or access it over your network:
- Local access:
http://localhost:3000 - LAN access:
https://your-machine.local:3001
LAN access requires HTTPS. The container generates a self-signed certificate automatically. Your browser will show a certificate warning the first time -- accept it and the exception will persist.
You'll be prompted for the username and password you set in
.env. - Local access:
Once the desktop is running in your browser you'll see that Obsidian is already launched.
Setting Up Obsidian
First, we'll set up Obsidian Sync:
-
Log into your Obsidian account.
-
Select which vault from your Obsidian Sync you want to use and Connect it.
-
When prompted for the vault location, set it to
/config/Obsidianand Create it. This path is bind-mounted tovaults/on the host, so your vault will persist across container rebuilds. -
Enter your E2E encryption password if needed and Unlock vault.
-
Start syncing and wait for it to finish.
Next, let's set up the command line interface so OpenClaw can use the CLI to talk to Obsidian:
-
Go to ⚙️ Settings > General and toggle the Command line interface to on.
-
Follow the prompt to register the CLI which will add the CLI to your system path.
-
Open a terminal and verify it works.
obsidian help -
If it worked, you will see the help for Obsidian CLI.
Next, we need to enable community plugins and enable them to be synced. If you're not using any plugins and never plan to, you can skip these steps:
-
Go to ⚙️ Settings > Community plugins and Turn on community plugins.
-
Also turn on Automatically check for plugin updates.
-
Go to Sync and toggle Active community plugin list and Installed community plugins to on. This will allow OpenClaw to manage plugins on your behalf and have them sync to your other devices. If you tell it to, of course.
-
Close Obsidian and relaunch it. Any plugins you have should now be loaded.
All of these settings are stored in config/obsidian/ on the host, and your vault data is stored in vaults/ on the host, so you only need to do this once. If you need to rebuild the container (e.g. to upgrade Obsidian or Node.js), just tear it down and bring it back up -- your login, Sync config, plugin settings, and vault data will all be there.
Finally, consider adding a README file to the root of your vault. OpenClaw's Obsidian skill reads this file before working in the vault to learn about its structure, folder conventions, templates, and any rules you want it to follow. If no README exists, OpenClaw will offer to help you create one.
Setting Up OpenClaw
OpenClaw is already installed and its gateway is running. You can access the web UI, but there's no AI provider configured, no skills installed, and no communication channels set up yet. We need to run through the onboarding process to set all of that up.
-
Launch a command-line Terminal if one isn't already open.
-
Start OpenClaw's onboarding process and follow the instructions:
openclaw onboard --skip-daemon --skip-healthThe
--skip-daemonflag skips the systemd service install, which doesn't work in a container. The gateway is already running via s6-overlay instead. The--skip-healthflag skips the health check, which expects systemd and reports a false failure. -
When prompted about Config handling, choose Use existing values. The gateway has already been configured for LAN access by the container's startup scripts.
-
Look at your openclaw.json file. This will be on your host system in the
config/openclawfolder or in the virtual desktop in~/.openclaw. Regardless of how you access it, look for your gateway auth token. It should be near the bottom of the file. Copy it. -
Navigate in your browser to https://127.0.0.1:18789/. In the Gateway Token field, paste your gateway auth token and click Connect.
-
You should now be able to chat with OpenClaw in the web interface. Say something to it like "Hello?" or my favorite, "Happy birthday!". It'll response and guide you through the rest of the setup process.
-
Try accessing OpenClaw from a web browser outside of the container as well. Be sure to use HTTPS and not HTTP. Use the same token as before when prompted. I recommend putting the token in a password manager.
-
You will be told that pairing is required. Go back into the browser in the virtual desktop and ask OpenClaw to approve the request. It might ask some clarifying questions.
-
You'll need to do this for each new browser you set up but you can ask OpenClaw to confirm the pairing request from any browser you have successfully pair and from any other private channel you use to talk to it.
Reference
Persistent Data
The following directories are bind-mounted to persist across container rebuilds. Only the things that matter are stored here -- everything else is ephemeral.
| Host path | Container path | Purpose |
|---|---|---|
config/obsidian/ | /config/.config/obsidian | Obsidian settings |
config/openclaw/ | /config/.openclaw | OpenClaw settings and workspace |
vaults/ | /config/Obsidian | Obsidian vault data |
Environment Variables
| Variable | Default | Description |
|---|---|---|
PASSWORD | (required) | Web desktop login password |
CUSTOM_USER | admin | Web desktop login username |
HOSTNAME | openclaw | Container hostname |
TITLE | OpenClaw Desktop | Browser tab title |
TZ | UTC | Container timezone |
HTTP_PORT | 3000 | Host port for web desktop (HTTP) |
HTTPS_PORT | 3001 | Host port for web desktop (HTTPS) |
OPENCLAW_PORT | 18789 | Host port for OpenClaw web UI |
| `DNS_SERV |
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
config/openclaw/skills/obsidian-desktop-cli/SKILL.md5.9 KBupstream ↗
--- name: obsidian-desktop-cli description: Search, read, create, and manage notes, tasks, and properties in an Obsidian vault using the Obsidian Desktop CLI user-invocable: false disable-model-invocation: false metadata: version: 0.1.0 author: Guy Royse <[email protected]> (https://guy.dev) --- # Obsidian Desktop CLI Interact with an Obsidian vault through the `obsidian` command line interface. The CLI communicates with the running Obsidian Desktop app via IPC. ## Targeting a Vault On first use, check which vaults are available: ```bash obsidian vaults verbose ``` If there is only one vault, that's the default. If there are multiple, ask the user which one they'd like to work with by default. Remember their choice for future conversations. If they want to change the default vault later, remember that choice as well. Most commands operate on the currently open vault. To target a specific vault by name, add `vault=<name>` to any command. ## Vault README Before working in a vault, read the README file in the vault root. It describes the vault's structure, folder conventions, templates, frontmatter patterns, and any rules for how you should interact with it. ```bash obsidian read file="README" ``` If no README exists, offer to create one with the user. Ask them about their vault's structure, conventions, and how they'd like you to work with it. ## Guardrails - **Appending** content to files is fine without asking, but tell the user what you're adding and where. - **Creating** new files is fine without asking. - **Modifying** existing text in a file requires user approval first. - **Moving or renaming** files requires user approval first. - **Removing or changing properties** requires user approval first. - **Deleting** files always requires explicit user confirmation. Never delete without asking. ## Error Handling If a CLI command fails, notify the user of the error. Do not retry automatically. Ask the user if they would like to retry. However, if a command fails with a sandbox-related error, retry it with `--no-sandbox` as the first argument. For example: `obsidian --no-sandbox read file="Note Name"`. If that works, use `--no-sandbox` for all subsequent commands. ## Common Commands ### Reading and Searching ```bash obsidian read file="Note Name" # Read by name (like wikilinks) obsidian read path="folder/note.md" # Read by exact path obsidian search query="search text" # Search vault for text obsidian search:context query="search text" # Search with matching line context obsidian file file="Note Name" # Show file info obsidian files # List all files obsidian files folder="Projects" # List files in a folder obsidian folders # List all folders obsidian outline file="Note Name" # Show headings obsidian backlinks file="Note Name" # List backlinks to a file obsidian links file="Note Name" # List outgoing links from a file obsidian tags # List all tags in the vault obsidian tags file="Note Name" # List tags on a file ``` ### Creating and Writing ```bash obsidian create name="Note Name" content="Content here" obsidian create name="Note Name" template="Template Name" obsidian append file="Note Name" content="New content" obsidian prepend file="Note Name" content="New content" ``` ### Organizing ```bash obsidian move file="Note Name" to="folder/path" # Move to folder obsidian move file="Note Name" to="folder/new.md" # Move and rename obsidian rename file="Note Name" name="New Name" # Rename in place obsidian delete file="Note Name" # Move to trash ``` ### Properties (Frontmatter) ```bash obsidian properties file="Note Name" # List properties on a file obsidian property:read file="Note Name" name="status" # Read a property obsidian property:set file="Note Name" name="status" value="done" obsidian property:set file="Note Name" name="tags" value="tag1,tag2" type=list obsidian property:remove file="Note Name" name="old-prop" ``` ### Tasks ```bash obsidian tasks # List all incomplete tasks obsidian tasks done # List completed tasks obsidian tasks file="Note Name" # Tasks in a specific file obsidian tasks verbose # Group by file with line numbers obsidian task file="Note Name" line=12 done # Mark a task as done obsidian task file="Note Name" line=12 todo # Mark a task as incomplete ``` ### Daily Notes ```bash obsidian daily:read # Read today's daily note obsidian daily:path # Get the daily note path obsidian daily:append content="New entry" # Append to daily note obsidian daily:prepend content="New entry" # Prepend to daily note ``` ### Bases ```bash obsidian bases # List all base files obsidian base:views # List views in current base obsidian base:query file="My Base" format=json # Query a base obsidian base:query file="My Base" view="View Name" # Query a specific view obsidian base:create file="My Base" name="Item Name" # Create a new item obsidian base:create file="My Base" name="Item" content="Details" ``` ### Sync ```bash obsidian sync:status # Check sync status obsidian sync on # Resume sync obsidian sync off # Pause sync ``` ## Notes - `file` resolves by name like wikilinks. `path` is an exact file path. - Quote values with spaces: `name="My Note"`. - Use `\n` for newline, `\t` for tab in content values. - Most commands default to the active file when `file` or `path` is omitted. - For detailed help on any command, run `obsidian help <command>`. - There are many more commands available. Run `obsidian help` for the full list.README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/guyroyse-openclaw-obsidian-desktop-config-openclaw-skills-obsidian-desktop-cli.md