Agent skill

Obsidian CLI

Obsidian vault integration via official CLI. An agent skill from sd0xdev/sd0x-harness.

MITAuto-check passedKnowledge Management

Install Obsidian CLI

skills CLI

$ npx skills add sd0xdev/sd0x-harness --skill obsidian-cli -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install sd0xdev/sd0x-harness obsidian-cli --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/obsidian-cli .claude/skills/obsidian-cli && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "obsidian-cli" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/obsidian-cli into .claude/skills/obsidian-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-cli", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/sd0xdev/sd0x-harness/tree/main/skills/obsidian-cli

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add sd0xdev/sd0x-harness --skill obsidian-cli -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install sd0xdev/sd0x-harness obsidian-cli --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/obsidian-cli .agents/skills/obsidian-cli && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "obsidian-cli" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/obsidian-cli into .agents/skills/obsidian-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-cli", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add sd0xdev/sd0x-harness --skill obsidian-cli -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install sd0xdev/sd0x-harness obsidian-cli --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/obsidian-cli .cursor/skills/obsidian-cli && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "obsidian-cli" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/obsidian-cli into .cursor/skills/obsidian-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-cli", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/sd0xdev/sd0x-harness.git --path skills/obsidian-cli

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add sd0xdev/sd0x-harness --skill obsidian-cli -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install sd0xdev/sd0x-harness obsidian-cli --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/obsidian-cli .gemini/skills/obsidian-cli && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "obsidian-cli" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/obsidian-cli into .gemini/skills/obsidian-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-cli", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install sd0xdev/sd0x-harness obsidian-cli

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add sd0xdev/sd0x-harness --skill obsidian-cli -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/obsidian-cli .github/skills/obsidian-cli && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "obsidian-cli" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/obsidian-cli into .github/skills/obsidian-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-cli", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add sd0xdev/sd0x-harness --skill obsidian-cli -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install sd0xdev/sd0x-harness obsidian-cli --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/obsidian-cli .opencode/skills/obsidian-cli && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "obsidian-cli" agent skill from https://github.com/sd0xdev/sd0x-harness/tree/main/skills/obsidian-cli into .opencode/skills/obsidian-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-cli", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: obsidian-cli
GitHub stars: 192
Token cost: ~1.1k tokens
SKILL.md length: 225 words
Files: 5 (incl. scripts, references)
Skills in repo: 91
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Obsidian vault integration via official CLI. An agent skill from sd0xdev/sd0x-harness.

Works in 4 steps: vault explicit argument → OBSIDIAN_VAULT environment variable → ~/.sd0x/obsidian-cli.env persisted default → …
: capturing dev artifacts to Obsidian vault
SKILL.md covers Trigger, When NOT to Use, Prerequisites and Workflow, plus 5 more sections
Runs Shell scripts from its folder; calls bash

What it does

Obsidian CLI is an agent skill from sd0xdev/sd0x-harness. Obsidian vault integration via official CLI. Use when: capturing dev artifacts to Obsidian vault, searching vault for context, appending to daily note, managing tasks in vault. Not for: general note-taking without Obsidian (use regular files), browsing Obsidian docs (use agent-browser). Output: vault search results, captured notes, task updates.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/integration-patterns.md`, `references/troubleshooting.md` and `scripts/obsidian-exec.sh`).

It sits in Knowledge Management, covering Note-taking and Browser automation. It works with Obsidian. The repository describes itself as: The harness layer for Claude Code — a reference implementation of harness engineering with hook-enforced dual review, state-machine gates that survive context compaction, and… The licence is MIT.

When your agent uses it

: capturing dev artifacts to Obsidian vault
Searching vault for context
Appending to daily note
Managing tasks in vault

Example prompts

“/obsidian-cli”

Requirements

A Bash shell
Pre-approved tools (allowed-tools): Bash(bash:*)

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

vault explicit argument
OBSIDIAN_VAULT environment variable
~/.sd0x/obsidian-cli.env persisted default
CLI-discovered active vault

What it can do on your machine

Read from SKILL.md and the folder at commit c9a2036. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash(bash:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
- bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Obsidian CLI loads about 1.1k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 225 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~90
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from sd0xdev/sd0x-harness at commit c9a2036, republished under its MIT licence (© sd0xdev). 225 words, ~1,112 tokens.

Download SKILL.mdSave it as .claude/skills/obsidian-cli/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: obsidian-cli
description: Obsidian vault integration via official CLI. Use when: capturing dev artifacts to Obsidian vault, searching vault for context, appending to daily note, managing tasks in vault. Not for: general note-taking without Obsidian (use regular files), browsing Obsidian docs (use agent-browser). Output: vault search results, captured notes, task updates.
allowed-tools: Bash(bash:*)

Obsidian CLI Integration

Trigger

Keywords: obsidian, vault, daily note, capture to vault, search vault, obsidian task

When NOT to Use

Obsidian is not installed or CLI is not enabled
User wants to edit markdown files directly (just use Read/Write)
User wants to browse Obsidian docs (use agent-browser)
User wants general task management without Obsidian

Prerequisites

Obsidian v1.12+ with CLI enabled (Settings > General > Command line interface)
Obsidian desktop app must be running (CLI uses IPC)

Workflow

/obsidian-cli [intent] [args]
     │
     ▼
 obsidian-preflight.sh --check
     │
     ├─ FAIL → Report issue + remediation
     │
     └─ OK → Resolve vault
              │
              ▼
         obsidian-exec.sh <intent> [args]
              │
              ├─ context → search vault, return results
              ├─ capture → write note/append to file
              ├─ daily   → append to daily note
              └─ task    → add/query tasks

Scripts

Script	Purpose	Invocation
`obsidian-preflight.sh`	Doctor + vault resolve + config	`bash scripts/run-skill.sh obsidian-cli obsidian-preflight.sh [--check\|--vault <id>\|--print-env]`
`obsidian-exec.sh`	Safe intent execution with timeout	`bash scripts/run-skill.sh obsidian-cli obsidian-exec.sh <intent> [args]`

Preflight

bash

# Check CLI + app + IPC readiness
bash scripts/run-skill.sh obsidian-cli obsidian-preflight.sh --check

# Set default vault
bash scripts/run-skill.sh obsidian-cli obsidian-preflight.sh --vault "My Vault"

# Print resolved env (for debugging)
bash scripts/run-skill.sh obsidian-cli obsidian-preflight.sh --print-env

Output lines:

STATUS=ok|error
VAULT=<resolved-vault-name>
OBSIDIAN_VERSION=<version>
ERROR=<message if STATUS=error>

Exec Intents

Intent	Args	CLI Commands Used
`context`	`--query <q> [--limit N]`	`obsidian search query= limit=`
`capture`	`--file <path> --text <content>`	`obsidian read path=`, `obsidian create path= content=`, `obsidian append path= content=`
`daily`	`--text <content>`	`obsidian daily:append content=`
`task`	`--add <text>` or `--list`	`obsidian daily:append content=`, `obsidian tasks daily`

bash

# Search vault for context
bash scripts/run-skill.sh obsidian-cli obsidian-exec.sh context --query "auth middleware"

# Capture a decision record
bash scripts/run-skill.sh obsidian-cli obsidian-exec.sh capture --file "dev/decisions/2026-02-28-auth.md" --text "..."

# Append to daily note
bash scripts/run-skill.sh obsidian-cli obsidian-exec.sh daily --text "- Implemented auth middleware refactor"

# Add a task
bash scripts/run-skill.sh obsidian-cli obsidian-exec.sh task --add "Review PR #42 auth changes"

Vault Resolution Policy

Deterministic precedence (first match wins):

--vault <name> explicit argument
OBSIDIAN_VAULT environment variable
~/.sd0x/obsidian-cli.env persisted default
CLI-discovered active vault

Verification

obsidian-preflight.sh --check outputs STATUS=ok
Vault resolution returns correct vault name
Each intent produces expected CLI output
Timeout handles IPC hang gracefully (exit 124)

References

references/integration-patterns.md — read when planning how to integrate Obsidian into dev workflow
references/troubleshooting.md — read when preflight fails or commands time out

Examples

bash

# First-time setup: check readiness and set default vault
/obsidian-cli --check
/obsidian-cli --vault "Dev Notes"

# During development: search for related notes
/obsidian-cli context --query "rate limiting implementation"

# After making a decision: capture it
/obsidian-cli capture --file "decisions/2026-02-28-rate-limit.md" --text "Decided to use sliding window..."

# End of session: log what was done
/obsidian-cli daily --text "- Completed rate limiting feature for API gateway"

Files

SKILL.md and 4 other files (scripts, references) in skills/obsidian-cli of sd0xdev/sd0x-harness.

SKILL.md
references/integration-patterns.md
references/troubleshooting.md
scripts/obsidian-exec.sh
scripts/obsidian-preflight.sh

Open the folder on GitHubat commit c9a2036

Compare with similar skills

Obsidian CLI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Obsidian CLI compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Obsidian CLI this skillsd0xdev/sd0x-harness	192	—	~1.1k	Automated safety check: Pass	MIT	yesterday
Obsidian Canvas BoardsAgriciDaniel/claude-obsidian	15k	—	~1.4k	Automated safety check: Pass	MIT	27 days ago
LLM Wikilewislulu/llm-wiki-skill	655	—	~3.7k	Automated safety check: Pass	None	5 mo ago
Obsidian Bases EditorAgriciDaniel/claude-obsidian	15k	—	~1.2k	Automated safety check: Pass	MIT	27 days ago
My LLM WikiMartinLwx/dotfiles	140	—	~2.7k	Automated safety check: Pass	None	18 days ago
Obsidian Knowledge BuilderMichael-OvO/obsidian-knowledge-agent	205	—	~917	Automated safety check: Pass	MIT	3 mo ago

Similar skills

Obsidian Canvas Boards
AgriciDaniel/claude-obsidian
Creates, inspects and updates Obsidian JSON Canvas boards in a vault, with text, file, link, group and edge nodes, using safe recoverable edits.
15k GitHub stars~1.4k tokensUpdated 27 days ago
Knowledge ManagementAuto-check passed
LLM Wiki
lewislulu/llm-wiki-skill
Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…
655 GitHub stars~3.7k tokensUpdated 5 mo ago
Knowledge ManagementAuto-check passed
Obsidian Bases Editor
AgriciDaniel/claude-obsidian
Explains, drafts and validates Obsidian Bases .base files, building filters, formulas and table, card or list views, and applying edits only through one inspected transaction.
15k GitHub stars~1.2k tokensUpdated 27 days ago
Knowledge ManagementAuto-check passed
My LLM Wiki
MartinLwx/dotfiles
Provides access to the user's personal wiki, including notes, research, project documentation, decisions, and archived knowledge.
140 GitHub stars~2.7k tokensUpdated 18 days ago
Knowledge ManagementAuto-check passed
Obsidian Knowledge Builder
Michael-OvO/obsidian-knowledge-agent
Turns PDFs, slides, syllabi, papers and transcripts into structured, teaching-quality Obsidian notes, matching how much structure is built to how much the material needs.
205 GitHub stars~917 tokensUpdated 3 mo ago
Knowledge ManagementAuto-check passed
LLM Wiki
CharlesHoskinson/sevenlayer
Builds and maintains a persistent, interlinked Obsidian-compatible markdown knowledge wiki in a git repo via three operations — ingest a source into linked pages, answer a question from the…
116 GitHub stars~1.5k tokensUpdated 1 mo ago
Knowledge ManagementAuto-check passed

Questions about Obsidian CLI

What does Obsidian CLI do?

Obsidian vault integration via official CLI. An agent skill from sd0xdev/sd0x-harness. Obsidian CLI is an agent skill from sd0xdev/sd0x-harness. Obsidian vault integration via official CLI.

When should I use Obsidian CLI?

Obsidian CLI fits situations like: : capturing dev artifacts to Obsidian vault; searching vault for context; appending to daily note; managing tasks in vault.

How do I install Obsidian CLI in Claude Code?

Run `npx skills add sd0xdev/sd0x-harness --skill obsidian-cli -a claude-code`. Or copy the skill folder (skills/obsidian-cli in sd0xdev/sd0x-harness) into .claude/skills/obsidian-cli in your project. Claude Code loads it when a task matches its description.

How do I install Obsidian CLI in Codex?

Run `npx skills add sd0xdev/sd0x-harness --skill obsidian-cli -a codex`. Or copy the skill folder (skills/obsidian-cli in sd0xdev/sd0x-harness) into .agents/skills/obsidian-cli in your project. Codex loads it when a task matches its description.

Can I use Obsidian CLI in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sd0xdev/sd0x-harness --skill obsidian-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/obsidian-cli, .gemini/skills/obsidian-cli, .github/skills/obsidian-cli and .opencode/skills/obsidian-cli in your project.

What does Obsidian CLI need to run?

Going by SKILL.md and its folder, Obsidian CLI needs a shell for the scripts in its folder and the command-line tools its instructions call (bash). Our summary lists: A Bash shell. Its frontmatter pre-approves these tools: Bash(bash:*).

Does Obsidian CLI access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Obsidian CLI safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Obsidian CLI use?

Obsidian CLI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Obsidian CLI use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Obsidian CLI?

Skills that share tags, products or a category with Obsidian CLI: Obsidian Canvas Boards (AgriciDaniel/claude-obsidian, 15k stars), LLM Wiki (lewislulu/llm-wiki-skill, 655 stars), Obsidian Bases Editor (AgriciDaniel/claude-obsidian, 15k stars) and My LLM Wiki (MartinLwx/dotfiles, 140 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Obsidian CLI?

sd0xdev (a GitHub user) maintains it in sd0xdev/sd0x-harness, which has 192 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 6, 2026.

Source: sd0xdev/sd0x-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Obsidian CLI

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Obsidian CLI Integration

Trigger

When NOT to Use

Prerequisites

Workflow

Scripts

Preflight

Exec Intents

Vault Resolution Policy

Verification

References

Examples

Files

Compare with similar skills

Similar skills

More from sd0xdev/sd0x-harness

Related

Questions about Obsidian CLI