wiki-cli
wiki-cli establishes the Obsidian CLI (v1.12+) as the primary transport layer for vault operations in claude-obsidian v1.7+, handling reads, writes, searches, and mutations without requiring MCP servers or REST API plugins. When the CLI is unavailable, the skill automatically falls back to direct filesystem access. Detection and fallback logic ensure reliable vault access across desktop and headless environments.
wiki-cli uses the Obsidian CLI as the preferred transport for reading, writing, and searching vault notes.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-05-28
wiki-cli uses the Obsidian CLI as the preferred transport for reading, writing, and searching vault notes. wiki-cli establishes the Obsidian CLI (v1.12+) as the primary transport layer for vault operations in claude-obsidian v1.7+, handling reads, writes, searches, and mutations without requiring MCP servers or REST API plugins. When the CLI is unavailable, the skill automatically falls back to direct filesystem access. Detection and fallback logic ensure reliable vault access across desktop and headless environments.
Use it when
- wiki-cli integrates Obsidian CLI into Claude workflows by routing vault operations through the CLI when available.
- wiki-cli uses Obsidian CLI as the primary transport because it requires no additional server setup or REST API plugins, unlike MCP.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
AgriciDaniel/claude-obsidian/wiki-cli · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What is the obsidian cli transport layer in wiki-cli?
wiki-cli establishes the Obsidian CLI (v1.12+) as the primary transport layer for vault operations, handling reads, writes, searches, and mutations without requiring MCP servers or REST API plugins. The CLI enables direct command-line access to your vault from claude-obsidian v1.7+, making it the preferred method for interacting with Obsidian vaults programmatically.
How do I use obsidian command line with Claude?
wiki-cli integrates Obsidian CLI into Claude workflows by routing vault operations through the CLI when available. You execute commands to read, write, search, and mutate notes directly. wiki-cli automatically detects whether the CLI is installed and configured, then uses it as the primary transport. If the CLI becomes unavailable, wiki-cli falls back to direct filesystem access to maintain vault access.
When should I use obsidian cli vs mcp?
wiki-cli uses Obsidian CLI as the primary transport because it requires no additional server setup or REST API plugins, unlike MCP. The CLI is faster for direct vault operations and works in headless environments. wiki-cli understands when to use the CLI and when to fall back to filesystem access, giving you the advantages of CLI performance without losing reliability when the CLI is unavailable.
What vault mutations can wiki-cli execute via CLI?
wiki-cli supports create, append, and patch frontmatter operations through Obsidian CLI. You can create new notes, append content to existing notes, and modify frontmatter properties. These mutations are executed reliably through the CLI transport layer, with automatic fallback to filesystem methods if needed.
How does wiki-cli detect available transport methods?
wiki-cli detects available transport methods by checking for Obsidian CLI installation and configuration, then establishing a fallback chain. If the CLI is available and responsive, wiki-cli uses it as the primary transport. If the CLI is unavailable or fails, wiki-cli automatically falls back to direct filesystem access, ensuring your vault remains accessible regardless of which transport method is available.
Can wiki-cli access daily notes, backlinks, and tags?
Yes, wiki-cli can access daily notes, backlinks, and tags through the Obsidian CLI transport layer. These vault features are available through the same CLI commands used for standard note operations, giving you full access to your vault's interconnected structure and metadata.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
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:
(truncated - see the full file via the links below)
File tree — 1 file
skills/wiki-cli/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Use Obsidian CLI as primary transport to read, write, and search vault notes”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
wiki-query lets you ask questions against your Obsidian vault and retrieves answers by reading cached content, indexes, and relevant pages. It supports three query depths—quick for simple facts, standard for most questions, and deep for comprehensive synthesis—and can file good answers back into your wiki to compound knowledge over time.
save captures valuable chat content and files it as a permanent wiki page with the right structure and metadata. It analyzes conversations to pick the best note type—synthesis, concept, source, decision, or session—then creates frontmatter, places the note in the correct folder, and updates your wiki's index and log. The skill respects your vault's organization mode and handles concurrent writes safely.
Canvas organizes visual references in Obsidian by letting you add images, PDFs, and wiki pages to canvas files with automatic positioning inside zones. It integrates with the /banana image capture skill and supports multiple operations like creating new canvases, managing zones, and listing existing canvases.
wiki-ingest reads external sources—files, URLs, or images—and populates your Obsidian vault by extracting entities and concepts, then creating or updating interconnected wiki pages. It handles delta tracking to skip unchanged sources, supports multiple vault organization modes, and uses file locking to safely coordinate concurrent writes across your knowledge base.
wiki-lint scans your Obsidian vault to surface structural problems: orphaned pages, broken wikilinks, missing cross-references, incomplete frontmatter, and empty sections. It generates a timestamped health report, updates Dataview dashboards, and can create visual canvas maps of your vault's domain structure.
wiki-retrieve upgrades vault search from page-level to chunk-level granularity, combining contextual prefixes, BM25 sparse retrieval, and dense reranking to reduce retrieval failures. Setup is opt-in with built-in privacy gates: run fully on-machine with synthetic prefixes, or opt into Anthropic API or claude CLI tiers for better context generation.
More skills wiki-mode (MIT) · obsidian-bases (MIT) · Obs Obsidian Bases (NOASSERTION)