wiki-cli
Wiki-cli is the default transport layer for claude-obsidian v1.7+ that uses the Obsidian CLI (built into Obsidian 1.12+) to read, write, search, and modify vault notes directly without requiring MCP servers or REST API plugins. Use this skill when you need reliable, low-latency vault operations on desktop installations of Obsidian, with automatic fallback to direct filesystem access when the CLI is unavailable.
git clone --depth 1 https://github.com/AgriciDaniel/claude-obsidian /tmp/wiki-cli && cp -r /tmp/wiki-cli/skills/wiki-cli ~/.claude/skills/wiki-cliSKILL.md
# Obsidian CLI read transport Use this skill only to detect transport and read or search a selected vault. The official executable is `obsidian`; binary presence alone does not prove it is usable. Resolve the installed product root from this skill's own location, not from the vault or current working directory: ```bash PRODUCT_ROOT=/absolute/path/to/installed/claude-obsidian DETECT_TRANSPORT="$PRODUCT_ROOT/scripts/detect-transport.sh" test -f "$DETECT_TRANSPORT" ``` ## Detect safely Probe without persisting host state: ```bash bash "$DETECT_TRANSPORT" --peek --vault "$VAULT" ``` Trust `available.cli.usable`, not merely `present` or exit status. A supported CLI can still be unavailable because the Obsidian app is not running, command line access is disabled, or its response is an error. Use filesystem reads as the portable fallback. Persist a refreshed `.vault-meta/transport.json` only when the user or setup workflow asks for a transport snapshot: ```bash bash "$DETECT_TRANSPORT" --force --vault "$VAULT" ``` That file is derived runtime configuration, not knowledge content. Preserve a valid `manual_override` recorded by the detector. ## Read and search Run official CLI commands from the selected vault so Obsidian resolves the correct workspace. Confirm supported syntax with the installed CLI before relying on optional commands. Typical read-only forms are: ```bash (cd "$VAULT" && obsidian read path="$NOTE") (cd "$VAULT" && obsidian search query="$QUERY") ``` Use read-only commands for backlinks, tags, or Bases results only when the detector reports the CLI ready. Otherwise read files under `$VAULT` directly and use `rg` for search. Reject absolute note arguments, traversal, symlinks, or resolved paths outside the selected vault. ## Mutation boundary Do not use CLI create, write, append, property-set, daily-append, move, rename, or delete commands. Do not replace those commands with direct filesystem writes. Any knowledge or configuration change must be expressed as one reviewed transaction through the portable core; see [operation transactions](../wiki/references/operation-transactions.md). Transport choice never changes mutation semantics. The CLI is an optional read surface, not a lock manager, transaction engine, or Git checkpoint mechanism. ## Checkpoint Observe actual capability, think about the least complex read transport, verify that every resolved path stays in the vault, and accept filesystem fallback when the CLI is not ready.
Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find everything about, research and file, go research, build a wiki on.
Create, inspect, and update Obsidian JSON Canvas boards with text, file, link, group, and edge nodes. Use for canvas status, canvas lists, visual maps, zones, spatial layouts, adding vault notes or media to a .canvas file, and requests such as create canvas, add to canvas, or put this on the canvas.
Plan and, with explicit network consent, use an optional external Defuddle cleaner to extract article-like HTTPS pages as Markdown. Use for defuddle, clean this URL, strip page clutter, readable Markdown from a web page, or preparing a web source for later wiki ingestion.
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
Explain, draft, or validate Obsidian Flavored Markdown syntax: properties, wikilinks, embeds, callouts, tags, comments, highlights, block references, math, and Mermaid. Use when the user explicitly requests Obsidian note formatting or syntax help, not for general Markdown or broad vault operations.
Save a user-selected answer, decision, insight, or session summary into an Obsidian vault as one reviewed transaction. Use only when the user explicitly asks to preserve specific conversation content, not when they supply a file or URL to ingest. Triggers: /save, save this, save that answer, file this conversation, save this analysis, keep this insight, preserve this chat result.
Apply the Fable-derived 10-stage OBSERVE, OBSERVE, LISTEN, THINK, CONNECT, CONNECT, FEEL, ACCEPT, CREATE, GROW loop to consequential or ambiguous reasoning and decisions. Use for think this through, deep think, architecture review, postmortem, tradeoff analysis, or challenges to assumptions. This is a reasoning review, not a deterministic vault health check or repair workflow.
>