Wiki CLI

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — USE REQUIREMENTS DISCLOSED FIRST: this skill works on your own Obsidian vault and resolves the installed claude-obsidian product root for its detector script, scripts/detect-transport.sh, which lives at the repository root OUTSIDE this skill's folder. Installing this listing copies only this skill's folder: without a full claude-obsidian installation the detector path it calls is absent. Its read surface is the official Obsidian command-line interface (the obsidian executable of the Obsidian app, an external dependency of your machine): binary presence alone does not prove it usable, since the app may not be running or command-line access may be disabled; when the CLI is not ready the skill falls back to direct filesystem reads and rg search of the vault. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Wiki CLI" for me. It detects and uses the official Obsidian command-line interface as a READ-ONLY transport for a selected vault: reading a note, searching, and, only when the detector reports the CLI ready, read-only forms for backlinks, tags or Bases results. Detection runs the repo's scripts/detect-transport.sh in --peek mode, which persists no host state, and trusts available.cli.usable rather than mere binary presence or exit status: a supported CLI can still be unusable because the Obsidian app is not running, command-line access is disabled, or its response is an error. A refreshed transport snapshot (.vault-meta/transport.json inside the vault) is persisted ONLY when you or a setup workflow asks for one (the --force form), preserving any manual_override the detector recorded; that file is derived runtime configuration, not knowledge content. CLI read commands run from inside the selected vault so Obsidian resolves the correct workspace, and absolute note arguments, traversal, symlinks and resolved paths outside the selected vault are rejected. The mutation boundary is absolute: it never uses CLI create, write, append, property-set, daily-append, move, rename or delete commands, and never replaces them with direct filesystem writes; any knowledge or configuration change is expressed as one reviewed transaction through the portable core (scripts/claude-obsidian.py, outside this folder). Transport choice never changes mutation semantics: the CLI is an optional read surface, not a lock manager, transaction engine or Git checkpoint mechanism. Repository: https://github.com/AgriciDaniel/claude-obsidian (the skill is the whole skills/wiki-cli/ folder at the pinned commit: SKILL.md only, 1 file) Pinned version: install the code at commit 2e545563172f97f02ecaaaab376ceea1246a0583 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/AgriciDaniel/claude-obsidian into a temporary folder, check out commit 2e545563172f97f02ecaaaab376ceea1246a0583, and copy the skills/wiki-cli/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 468df53c8712379c1681a897225e898771ca36f21e4e6e02dc8eec9f02fc8c87 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file only: SKILL.md. The detector it runs (scripts/detect-transport.sh) and the portable core its mutation boundary points to (scripts/claude-obsidian.py) live outside this folder, in the full claude-obsidian product root; the Obsidian CLI itself is the official app executable on my machine, not bundled here. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no transport is detected, no vault is read and no snapshot is written. - At use time the CLI surface is read-only (read, search, and backlinks/tags/Bases reads when the detector says usable), run from inside my selected vault, with a filesystem-plus-rg fallback when the CLI is not ready. Detection in --peek mode persists nothing; a .vault-meta/transport.json snapshot is written only when I or a setup workflow asks for one. - It never mutates through the CLI and never writes files directly: no create/write/append/property-set/move/rename/delete CLI commands. Any change goes through one reviewed transaction via the portable core, under the same APPROVAL_SHA256 review pattern as the rest of the family. - Do not run the detector, do not probe or read any vault, do not write any transport snapshot, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole wiki-cli folder into the agent's skills directory, in a folder named exactly "wiki-cli", keeping its single file (SKILL.md) at its root. 4. Verify with no network calls: frontmatter valid (name: wiki-cli), the 1 file in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that a full claude-obsidian installation (detector script and portable core at the product root) and my own Obsidian vault are required to use it, that the official Obsidian CLI is an external app dependency with a filesystem fallback, and that its surface is read-only, mutations going through the transaction core). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.