Check whether the official Obsidian command-line interface is ready, then use it to read and search a selected vault. Access supported backlinks and tags, with direct file reading as a fallback when the interface is unavailable.
Detect and use the official Obsidian command-line interface for read-only vault access; use for wiki-cli, Obsidian CLI, Obsidian read, Obsidian search, vault transport, which transport, transport detection, backlinks, tags, or Obsidian command line. Mutations always go through the claude-obsidian transaction core.
Review the instructions the agent will receive before you install.
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:
PRODUCT_ROOT=/absolute/path/to/installed/claude-obsidian
DETECT_TRANSPORT="$PRODUCT_ROOT/scripts/detect-transport.sh"
test -f "$DETECT_TRANSPORT"
Every ../wiki/references/ link in this file resolves the same way, relative
to this skill's own directory under $PRODUCT_ROOT, never relative to the
selected vault's wiki/ directory.
Probe without persisting host state:
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 "$DETECT_TRANSPORT" --force --vault "$VAULT"
That file is derived runtime configuration, not knowledge content. Preserve a
valid manual_override recorded by the detector.
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:
(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.
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.
Transport choice never changes mutation semantics. The CLI is an optional read surface, not a lock manager, transaction engine, or Git checkpoint mechanism.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Research a defined topic within agreed limits and produce a cited report that distinguishes evidence, inference, contradictions, and gaps. Public web access requires consent, and saving findings or merging them into existing Obsidian notes receives separate review.
Create and update Obsidian canvas boards by arranging notes, media, text, and links into visual maps. Inspect existing boards for missing files and broken connections, and preview validated changes before applying them through recoverable transactions.
Prepare readable Markdown from HTTPS article pages using an optional external Defuddle cleaner. The workflow checks URLs, requires network consent and executable review, previews extracted content, and can retain the cleaned source separately from wiki ingestion.
Build and validate Obsidian Bases files that display notes as tables, cards, or lists. Define filters, calculated values, displayed properties, and summaries to create reading lists, task trackers, and other database-like views of existing notes.
Draft and check Obsidian notes using its Markdown extensions. Get help with note properties, internal links, embedded content, callouts, equations, and Mermaid diagrams, with checks for formatting consistency and locally verifiable link targets.
Preserve a selected answer, decision, insight, or conversation summary as an Obsidian note. Check for duplicates, retain uncertainty, and preview the note together with related index and log updates before applying the reviewed changes.