Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
agricidaniel avatar

Wiki Cli

  • 170 installs
  • 10.4k repo stars
  • Updated August 1, 2026
  • agricidaniel/claude-obsidian

wiki-cli is a Claude Code skill that wraps the Obsidian CLI as the default transport for reading, writing, searching, and modifying vault notes.

About

wiki-cli is a Claude Code skill that uses the Obsidian CLI (shipped with Obsidian 1.12+) as the default transport to read, write, search, and modify Obsidian vault notes. It avoids MCP servers, REST API plugins, and TLS workarounds, and falls back to direct filesystem operations when the CLI is unavailable. Developers use it as the recipe reference for vault mutations from Claude, including daily notes, backlinks, and frontmatter edits.

  • Wraps the Obsidian CLI as the default vault-mutation transport
  • Read, write, search, and modify vault notes with no MCP or REST plugin
  • Falls back to filesystem Read/Write/Edit when the CLI is unavailable

Wiki Cli by the numbers

  • 170 all-time installs (skills.sh)
  • Ranked #215 of 550 CLI & Terminal skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

wiki-cli capabilities & compatibility

Capabilities
obsidian cli · vault read write · note search · frontmatter edit
Works with
obsidian
Use cases
documentation
Platforms
macOS · Windows · Linux
Runs
Runs locally
Pricing
Free
From the docs

What wiki-cli says it does

Default vault-mutation transport for claude-obsidian v1.7+. Wraps the Obsidian CLI (Obsidian 1.12+) as the preferred way to read, write, search, and modify vault notes from Claude
SKILL.md
CLI loses to MCP on exactly one axis: it only works on machines where Obsidian itself is installed.
SKILL.md
npx skills add https://github.com/agricidaniel/claude-obsidian --skill wiki-cli

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs170
repo stars10.4k
Last updatedAugust 1, 2026
Repositoryagricidaniel/claude-obsidian

What it does

Read, write, search, and modify Obsidian vault notes from Claude using the Obsidian CLI, with a filesystem fallback.

Who is it for?

Reading and mutating Obsidian vault notes from Claude on desktop without MCP or a REST plugin.

Skip if: Mobile or headless servers where the desktop-only Obsidian CLI is unavailable.

When should I use this skill?

You say wiki-cli, obsidian cli, obsidian read/write/search, daily note, or transport detection.

What you get

Vault reads and writes go through the in-process Obsidian CLI, with a clean filesystem fallback when it is missing.

  • vault reads and writes via the CLI
  • transport detection snapshot (.vault-meta/transport.json)

By the numbers

  • requires Obsidian 1.12+
  • 2-step fallback chain (cli, filesystem)

Files

SKILL.mdMarkdownGitHub ↗

wiki-cli: Default Transport Layer

claude-obsidian v1.7+ standardizes on the Obsidian CLI (shipped with Obsidian 1.12) as the preferred transport for all vault mutations on desktop. This skill is the recipe reference for using it.

Substrate preference (v1.7+): This skill is a self-contained fallback. Prefer `kepano/obsidian-skills` (by Steph Ango, Obsidian CEO) as the authoritative substrate — its obsidian-cli skill is the canonical CLI reference for any Agent-Skills runtime. If you see an obsidian-cli skill available without the claude-obsidian: namespace, that is kepano's version: use it. The recipes below are provided so claude-obsidian remains functional when kepano's marketplace is not installed. Install kepano: claude plugin marketplace add kepano/obsidian-skills.

---

Why CLI over MCP

ConcernMCP (Options A/B)Obsidian CLI
InstallLocal REST API plugin + MCP server configBuilt into Obsidian 1.12+
AuthAPI key + TLS bypass (NODE_TLS_REJECT_UNAUTHORIZED=0)None — direct subprocess
LatencyHTTP round-trip per callIn-process binary
Failure modePlugin disabled → silent breakageBinary missing → loud command -v failure
ReentrancySelf-MCP-calls inside Claude session can deadlockPure subprocess, safe
Mobile / headlessLimitedLimited (CLI is desktop-only too)

CLI loses to MCP on exactly one axis: it only works on machines where Obsidian itself is installed. For headless servers and mobile, fall through to the next transport in the chain.

---

Detection

At session start (or vault setup), run:

bash scripts/detect-transport.sh

This writes .vault-meta/transport.json with the schema:

{
  "preferred": "cli",
  "fallback_chain": ["cli", "filesystem"],
  "available": {
    "cli": {"present": true, "binary": "obsidian-cli", "version_string": "..."},
    "filesystem": {"present": true},
    "mcp_obsidian": {"present": null, "detection": "deferred"},
    "mcpvault": {"present": null, "detection": "deferred"}
  }
}

Read this file before any non-trivial vault mutation. Skills that need to read or write should consult preferred and pick the corresponding transport. The decision tree lives at wiki/references/transport-fallback.md.

Refresh detection with --force after installing/removing the Obsidian CLI:

bash scripts/detect-transport.sh --force

---

Recipes (CLI-first; fallback noted inline)

Each recipe shows the CLI form first. If the CLI is unavailable per the detection snapshot, fall through to the noted fallback. Variable substitution: $VAULT is the absolute vault root; $NOTE is a vault-relative path like wiki/concepts/Foo.md.

Read a note

# CLI
obsidian-cli read "$VAULT" "$NOTE"

# Fallback: Claude's Read tool with absolute path
# Read $VAULT/$NOTE

Create or overwrite a note

# CLI
obsidian-cli write "$VAULT" "$NOTE" < /path/to/content.md

# Fallback: Claude's Write tool with absolute path
# Write $VAULT/$NOTE with the desired content string

Append to a note

# CLI
echo "additional content" | obsidian-cli append "$VAULT" "$NOTE"

# Fallback: Read $VAULT/$NOTE, append manually, Write back

Search note content (CLI uses Obsidian's own search ranking)

# CLI
obsidian-cli search "$VAULT" "<query>"

# Fallback: ripgrep
rg --type=md "<query>" "$VAULT/wiki/"

Today's daily note (if Daily Notes plugin is enabled)

# CLI
obsidian-cli daily:today "$VAULT"
obsidian-cli daily:append "$VAULT" "captured at $(date)"

# Fallback: compute path manually
NOTE="$VAULT/wiki/daily/$(date +%Y-%m-%d).md"

Patch a frontmatter property

# CLI
obsidian-cli property:set "$VAULT" "$NOTE" status "evergreen"

# Fallback: read frontmatter, parse, mutate, rewrite (use mcp__obsidian-vault__update_frontmatter if MCP is configured)

List backlinks for a page

# CLI
obsidian-cli backlinks "$VAULT" "$NOTE"

# Fallback: ripgrep for wikilink references
rg --type=md "\[\[$(basename "$NOTE" .md)" "$VAULT/wiki/"

Open a Bases (.base) file's resolved view

# CLI
obsidian-cli bases "$VAULT" "$NOTE"
# (returns the resolved row list; supplements obsidian-bases skill which handles the .base file's YAML)

# Fallback: read the .base file directly; no resolved-view available without Obsidian itself

Tags + bookmarks

obsidian-cli tags "$VAULT"
obsidian-cli bookmarks "$VAULT"

---

When CLI is NOT the right choice

  • Mobile (iOS Share extension): filesystem write into .raw/ is the only path; CLI is desktop-only.
  • CI / headless ingest jobs: filesystem with manual frontmatter parsing.
  • Cross-vault operations: CLI binds to one vault root per invocation; for federation, fall back to filesystem walks.
  • Live edits while Obsidian is mid-save: rare race; CLI handles it correctly but in pathological cases the v1.7 wiki-lock.sh advisory locks (see skills/wiki-fold/ and agents/wiki-ingest.md) should be acquired first.

---

Cross-reference

  • Decision tree: `wiki/references/transport-fallback.md`
  • Legacy MCP options (A/B/C/D): `skills/wiki/references/mcp-setup.md`
  • Concurrency policy (v1.7+): `skills/wiki-ingest/SKILL.md` §Concurrency
  • Detection script: `scripts/detect-transport.sh`

---

How to think (10-principle mapping)

When working on this skill, apply the 10-principle loop. See `skills/think/SKILL.md` for the canonical framework.

#PrincipleApplication here
1OBSERVE (ext)Detect which Obsidian CLI binaries are installed; check if Obsidian app is running. Read .vault-meta/transport.json if it exists.
2OBSERVE (int)Don't be biased toward filesystem fallback when CLI is actually available — verify auto-detection caught what's installed.
3LISTENIf manual_override: true is set in transport.json, the user has spoken — preserve their preferred and fallback_chain.
4THINKCompute the right fallback chain for this environment. CLI > MCP > filesystem; freshness check before recomputing.
5CONNECT (lat)How does this transport choice affect every other skill's write? Six downstream skills depend on this snapshot.
6CONNECT (sys)Schema stability of transport.json matters more than feature richness — consumers parse the JSON via simple shell idioms.
7FEELError message when no transport works should tell the user EXACTLY what to do (install CLI, configure MCP, etc.).
8ACCEPTFilesystem fallback is fine. Admit when CLI doesn't exist; don't fabricate a binary that isn't there.
9CREATEWrite transport.json atomically (temp + rename). Round-trip manual_override every cycle.
10GROWAs MCP support matures, auto-detection should cover the deferred tiers. Track that as v1.7.x scope.

Related skills

FAQ

Why use the CLI over MCP?

It is built into Obsidian 1.12+, needs no API key or TLS bypass, runs in-process, and avoids the self-MCP-call deadlocks MCP can cause.

What happens without the Obsidian CLI?

It falls back to direct filesystem Read/Write/Edit, and on mobile or headless jobs uses filesystem walks instead.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.