Wiki Mode

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 runs through TWO scripts that live at the repository root OUTSIDE this skill's folder: the portable core scripts/claude-obsidian.py and the mode helper scripts/wiki-mode.py, together with the shared contracts under skills/wiki/references/ in that same product root (in particular the operation-transaction contract). Installing this listing copies only this skill's folder (its SKILL.md plus its six methodology templates): without a full claude-obsidian installation (the core, the mode helper, its contracts, python3 to run them, and a selected user vault) the skill cannot run as designed. The family orchestrator is the separate wiki skill of the same repository. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Nothing is sent anywhere at use time either. One write is real and disclosed here: changing the vault mode is a configuration operation that writes exactly one file, .vault-meta/mode.json inside your vault, and only as a dry-run-first transaction approved with its hash (APPROVAL_SHA256 pattern) through the core; the helper's legacy direct-write set action must not be used to bypass that workflow. Reading the mode and routing suggestions write nothing. Install "Wiki Mode" for me. It reads or configures your vault's filing methodology and suggests destinations for planned knowledge creation under one of four modes: Generic (type-based folders such as sources, entities, concepts and sessions), LYT (atomic notes under wiki/notes/ connected through MOCs), PARA (Projects, Areas, Resources or Archives chosen by actionability), or Zettelkasten (flat atomic notes with time-sortable, collision-resistant identifiers and explicit links). It does not save content and does not migrate notes. If .vault-meta/mode.json is absent it uses generic; if the file exists but is invalid it fails closed and the configuration must be repaired through a reviewed operation before any routing: it never silently substitutes Generic for corrupt user configuration. Routing goes through the mode helper (get, config, and route for a concept or a source): the helper validates the selected vault, confines paths, sanitizes names and prints a suggestion only; a calling skill may override the suggestion when you supply a more specific project, area, MOC or parent note, but its eventual writes still go through one operation transaction. The six bundled templates (LYT atomic and MOC, PARA area, project and resource, Zettelkasten atomic) are structural guidance using the canonical type values and a separate flat methodology_role property; a resource template describes a topic collection, while a particular captured source uses type source instead, and structural MOCs use an explicit destination since meta is not a routable new-note type. Changing mode is one configuration operation, dry-run first: read the current mode.json, validate the requested mode as exactly generic, lyt, para or zettelkasten, preserve the other mode-specific settings, pin a UTC timestamp and operation ID, preview the canonical transaction (which records the current target hash and limits the write to .vault-meta/mode.json), show the old mode, new mode, exact changed path and complete preview, and apply only by regenerating that exact plan with its approved_plan_sha256. Changing mode affects routing for future operations only: it never bulk-creates folders, moves notes, rewrites wikilinks or migrates existing pages as a side effect; any migration is a distinct reviewed operation with its own hashes and transaction. Repository: https://github.com/AgriciDaniel/claude-obsidian (the skill is the whole skills/wiki-mode/ folder at the pinned commit: SKILL.md plus 6 methodology templates under templates/, 7 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-mode/ 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 47d267864295d6cda09c4f7f767cf24786ecfb843341506e7472c29ba870a2cf - templates/lyt/atomic-template.md: SHA-256 5e72419136266bf8f59f9f48d321a808444cd219ab73eb5e27ef0bfcfef517e3 - templates/lyt/moc-template.md: SHA-256 3fa8e86102a20f2d054d2973e848c50630843db249c8625193b3646f983cb257 - templates/para/area-template.md: SHA-256 7d5afa7f9686ce229b91c81ea7016787dd5414cef390089d4ba49e890d168689 - templates/para/project-template.md: SHA-256 d9e436d94226f98841c642d5b282fee7eeb0fc5060284d702ee3106cfba56d1b - templates/para/resource-template.md: SHA-256 2293dfdfad78c8c12157464ab4debfe4f17afdd77f5d200c7b0d17510303ed63 - templates/zettel/atomic-template.md: SHA-256 2c491ddb488920b7c46674d8ac77b0f69a2ca0e5b4a7b7e533f06bedd58cacba 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 7 files: SKILL.md plus 6 templates (templates/lyt/atomic-template.md, templates/lyt/moc-template.md, templates/para/area-template.md, templates/para/project-template.md, templates/para/resource-template.md, templates/zettel/atomic-template.md). The two scripts it runs (scripts/claude-obsidian.py and scripts/wiki-mode.py) and the operation-transaction contract live outside this folder, in the full claude-obsidian product root. - 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 read or configured. - At use time it sends nothing anywhere. Reading the mode and getting a routing suggestion write nothing; the skill does not save content, write knowledge pages or move existing notes. - The only write it can perform is a mode change: one configuration transaction, dry-run first, limited to .vault-meta/mode.json in my vault and applied only with the approval hash (APPROVAL_SHA256 pattern) through the core. The mode helper's legacy direct-write set action and any setup script must not be used to bypass that workflow, and a mode change never migrates, moves or rewrites existing notes. - Do not read any vault mode, do not run the mode helper or the core, 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-mode folder into the agent's skills directory, in a folder named exactly "wiki-mode", keeping its 7 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: wiki-mode), the 7 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, mode helper and contracts at the product root) and my own Obsidian vault are required to use it, that routing suggestions write nothing, and that the only possible write is a reviewed mode change limited to .vault-meta/mode.json). 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.