obsidian-official-cli-headless
Install and adapt the official Obsidian CLI for headless Linux servers by using a non-root user, Xvfb virtual display, ACL-based vault access, and an obs wrapper command. Use when the user wants the official Obsidian CLI (not notesmd-cli) on a Debian/Ubuntu-like machine without a normal desktop session, or when root/GUI/display constraints break native CLI use.
Why use this skill?
Deploy the official Obsidian CLI on headless Linux with Xvfb and ACLs. Automate your knowledge management workflows with this official Obsidian integration.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/darinrowe/obsidian-official-cli-headlessWhat This Skill Does
The obsidian-official-cli-headless skill provides a specialized deployment strategy for running the official Obsidian desktop application in CLI mode on headless Linux servers. Because the official Obsidian binary expects a graphical environment (X11/Wayland), this skill automates the complex configuration required to simulate a desktop display using Xvfb (X Virtual Framebuffer). It installs the official .deb package, creates a dedicated, isolated 'obsidian' service user for enhanced security, configures Access Control Lists (ACLs) to manage vault permissions without altering root ownership, and generates a robust /usr/local/bin/obs wrapper script. This wrapper manages the virtual display session automatically, allowing you to execute Obsidian CLI commands like daily note management and vault searching as if you were on a standard desktop environment, all without the overhead of a full GUI desktop manager.
Installation
Installation is streamlined through the OpenClaw hub. Run the following command in your terminal: clawhub install openclaw/skills/skills/darinrowe/obsidian-official-cli-headless. The skill requires root privileges to configure the system environment, install dependencies, and set up user-level permissions. Ensure your system meets the Debian/Ubuntu prerequisites before initiation.
Use Cases
This skill is designed for scenarios where Obsidian needs to be the primary knowledge management engine in a server environment. Typical use cases include: 1) Automating log ingestion or daily journal entries via cron jobs on a remote Linux server. 2) Programmatic interaction with complex Obsidian vaults that require official plugin support and engine features that lightweight CLI tools cannot provide. 3) Migrating a desktop workflow to a centralized server environment without abandoning the Obsidian application's core functionality.
Example Prompts
- "I need to automate my daily notes on my server. Can you install and configure the official Obsidian CLI for my vault located at /var/data/my-vault?"
- "My server is headless and I keep getting display errors when trying to run the obsidian binary. Please set up the obsidian-official-cli-headless skill to fix this."
- "Verify that my current Obsidian CLI installation is working correctly by checking the vault path and performing a search for 'meeting notes'."
Tips & Limitations
This skill is specifically tuned for the official Obsidian distribution; do not attempt to use it with third-party tools like notesmd-cli. Because it leverages Xvfb, it requires significant RAM for a server environment—ensure your host has at least 512MB-1GB of spare memory to handle the virtual display. We strongly recommend using ACLs to provide the 'obsidian' user with read/write access to your vault rather than changing directory ownership, as this maintains system integrity. Please be aware that this does not provide a visual UI; all interactions are strictly via the CLI, and GUI-heavy plugins may require specific configuration adjustments to run effectively in a headless state.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-darinrowe-obsidian-official-cli-headless": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-write, file-read, code-execution
Related Skills
openclaw-backup-restore
Backup and restore OpenClaw configuration, agents, sessions, and workspace to/from a private Git repository. Use when the user wants to manually trigger a backup, migrate to a new machine, or restore from a previous state.
multi-agent-filesystem-governance
Govern filesystem organization and file-operation decisions in multi-agent environments. Use when deciding where files should live across agent-private workspaces, shared resources, archives, downloads, scripts, notes, knowledge vaults, and code project folders; when defining directory conventions; when triaging downloads; when preventing cross-agent overwrites; or when standardizing file placement and lifecycle rules for reusable agent setups.
git-backed-obsidian-cli-workflows
Use the official Obsidian CLI for note workflows in a Git-backed vault, including search, read, links/backlinks-style queries, daily-note operations, and lightweight note writes that auto-sync after successful write operations. Use when the official Obsidian CLI is already installed and usable on any supported environment, and the task is about querying or updating notes in an Obsidian vault with Git-backed backup behavior.
git-workflows-pro
Handle advanced git workflows and recovery tasks. Use when the user needs help with interactive rebase, commit cleanup, conflict resolution, reflog recovery, cherry-pick, stash, worktree, bisect, submodule vs subtree decisions, sparse checkout, branch archaeology, or undoing dangerous history mistakes in real repositories.
github-private-repo-ssh-routing
Diagnose and manage SSH keys, host aliases, and Git remotes for GitHub private repositories in multi-repo environments. Use when deploy keys collide, a machine manages multiple private repos, automation or backup scripts push to GitHub, or errors like "Permission denied (publickey)" / "Repository not found" appear despite the repo existing.