Wiki

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 is the ORCHESTRATOR skill of the claude-obsidian family. It works on a separate Obsidian vault of yours (never the product/plugin root itself, which is code, while the selected vault is data) and runs through the portable core of the repository, scripts/claude-obsidian.py, which lives at the repository root OUTSIDE this skill's folder. This listing's folder does carry the family's shared contracts and guidance as its 14 bundled references/ files (including the operation-transaction and provenance contracts); the other family skills link to those same references. Installing this listing copies only this skill's folder: without a full claude-obsidian installation (the core, python3 to run it, and a vault you select) its commands cannot run as designed, and the specialist wiki-* skills it routes to are separate listings that must be installed separately. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Baseline setup requires no network egress: the skill does not fetch templates, plugins or remote content unless you separately approve the destinations and budget. Optional reference material bundled in this folder describes adapters that are NOT part of baseline setup and are read only when you explicitly ask (an external MCP read transport, the Obsidian Local REST API adapter, optional plugins and Dataview, local Git/checkpoint setup). Install "Wiki" for me. It initializes, adopts and routes work for a separate Obsidian knowledge vault through the portable claude-obsidian core. On its own it does the orchestration work: it resolves the selected vault in a fixed order (explicit --vault, then the CLAUDE_OBSIDIAN_VAULT environment variable, then the nearest .claude-obsidian.json, then an unambiguous initialized vault at or above the current directory) and fails closed when selection is missing or ambiguous; it scaffolds a new vault or adopts an existing Obsidian vault through the core's deterministic init and adopt commands, which are dry-run by default, show the selected path and the changed-path preview, and apply only when the reviewed plan's hash is passed back unchanged (approved-plan-sha256, the family's APPROVAL_SHA256 pattern); setup is non-destructive by default, creates no upstream Git remote, and --force is used only when you have reviewed the conflicts and explicitly approved replacement. For a domain-specific scaffold it establishes the baseline first, then reads the bundled modes reference and drafts the additional pages and configuration as one operation-level transaction; it never mutates vault files with host Write/Edit tools or an Obsidian transport. What it delegates, without silently broadening your intent: ingesting supplied sources goes to wiki-ingest, answering from existing vault knowledge to wiki-query, saving a specific conversation result to save, researching the public web under a budget to autoresearch, checking vault health to wiki-lint, rolling up log entries to wiki-fold, and working with a canvas to canvas; drafting a cited glossary or consolidating overlapping notes also goes to wiki-ingest, with an explicitly reviewed scope. Query is read-only through this router too: persistence from a query must be an explicit, separately scoped Save operation, and no transcript is captured and no hot cache updated merely because a session ended. Every mutation follows the bundled operation-transaction contract: one logical operation produces one inspected and recoverable claude-obsidian.transaction.v1 bundle, parallel agents may return drafts and evidence only while the orchestrator merges them and applies once, every canonical page create or removal includes an active index or MOC update in that bundle (the overview is updated only when the stable high-level picture changed), raw source payloads are create-only, and there are no automatic commits; a Git checkpoint runs separately, only when you explicitly want one, and on conflict the bundle is re-read and rebuilt while an interruption is handled with transaction recover. Provenance follows the bundled provenance contract: unsupported evidence stays unsupported and no source, quote, date, locator or confidence is ever invented. Its 14 bundled references are read conditionally, only the one the current request needs: frontmatter schemas, CSS snippets, Git setup, optional plugins, MCP setup, the REST API adapter, Dataview, knowledge recipes, coordination across editors or machines, install modes, model guidance, modes, the operation-transaction contract and the provenance contract (a few references also point to docs at the repository root, outside this folder). Repository: https://github.com/AgriciDaniel/claude-obsidian (the skill is the whole skills/wiki/ folder at the pinned commit: SKILL.md plus its 14 bundled reference files under references/, 15 files in total) 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/ 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 562c92afa2ff44b3084ae5d4c2b9a3e4d09bfd20b586fc27d275c4b15cdd8662 - references/coordination.md: SHA-256 33315ec7bfe6f6dc63d10c0a75dc6ec26bd4860f039313f1d22534bbed5e37b6 - references/css-snippets.md: SHA-256 1b493d6b601a2ebc8ace6db75acfa84663ecfb8633f2a1b93da874793615f625 - references/dataview.md: SHA-256 d4b16761560fc258eefe9a4fdad6ca774154e5ac24a3573cc91b02e8037113be - references/frontmatter.md: SHA-256 650cb8ff10937d2289b48412a9ac7438d9d5eefa68a58fe99630d3d9102d224e - references/git-setup.md: SHA-256 932c92d490ac7f998065d9188d47b571578cb8ba60258cf5e401602cc77c0714 - references/install-modes.md: SHA-256 e144fd3d74f7ad6495f5b9d5c29e225e9ccf8572d91f4af40d913a278433c5b0 - references/knowledge-recipes.md: SHA-256 30c5bbad1653a199446babba9b2aeee84965ede5d9cd7298ff48c58f34c7b256 - references/mcp-setup.md: SHA-256 56353117c309c6d7ea65128a66885d29a3a34c96b2c974c9f4e8785b255a718a - references/model-guidance.md: SHA-256 5a28662268be6d43e52fb2f65eb424713e8031132f2b0ffb69bb10ee94587d78 - references/modes.md: SHA-256 affecc6cc55d8344593d846ef94a72baec4faacdb654c0d31721176779926eca - references/operation-transactions.md: SHA-256 182a333e314f948d42504d48505bb76550276db17a27ae6081acfa9273330cd1 - references/plugins.md: SHA-256 cac30ee29fd762fdd91dfff2d2d6759d3d91ea5a3e1912ebd3309174cdc8c76f - references/provenance.md: SHA-256 8c773a95a36bd23f6482c4595c70b8ba9679122c9e48986d26955bfdc176c418 - references/rest-api.md: SHA-256 79179ede8e8b8279ac0ec9982c616b86b548428edf14175e86c0dd02e5932ffb 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 15 files: SKILL.md plus 14 references (references/coordination.md, references/css-snippets.md, references/dataview.md, references/frontmatter.md, references/git-setup.md, references/install-modes.md, references/knowledge-recipes.md, references/mcp-setup.md, references/model-guidance.md, references/modes.md, references/operation-transactions.md, references/plugins.md, references/provenance.md, references/rest-api.md). The core it runs (scripts/claude-obsidian.py) lives outside this folder, in the full claude-obsidian product root, and the specialist skills it routes to are separate listings. - 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 vault is created, adopted, read or routed. - At use time, on its own it resolves the vault, runs the core's init/adopt scaffolding dry-run first and applies only with the reviewed plan hash (APPROVAL_SHA256 pattern), non-destructively and with no upstream Git remote; baseline setup fetches nothing from the network. Everything else is delegation: ingest to wiki-ingest, answers to wiki-query, saving to save, web research to autoresearch, health checks to wiki-lint, log rollups to wiki-fold, canvas work to canvas. - Every mutation it applies is one inspected claude-obsidian.transaction.v1 bundle including the index or MOC update, with create-only raw payloads and no automatic commits; a Git checkpoint happens only as a separate step I explicitly request. Optional adapters described in its references (MCP read transport, Local REST API, plugins, Dataview) are evaluated only when I explicitly ask. - Do not initialize or adopt any vault, do not run the core, do not route any operation, 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 folder into the agent's skills directory, in a folder named exactly "wiki", keeping its 15 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: wiki), the 15 files 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 (portable core at the product root) and a separate Obsidian vault of mine are required to use it, that the specialist wiki-* skills it routes to are installed separately, and that its own scaffolding applies only dry-run first with the reviewed plan hash). 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.