wiki-tourlisted

Generate a guided, pedagogical reading tour through a vault — an ordered walkthrough that takes a newcomer from "what is this?" to "I get how it fits together", computed from the knowledge graph's link topology. Use when the user says "give me a tour of this vault", "where do I start", "walk me through my notes", "onboarding path", "/wiki-tour", "fais-moi visiter le vault", "parcours guidé", "par où commencer", or wants a learning path through a vault or one of its projects/topics.
tboome33/obsidian-mcp-router · ★ 1 · AI & Automation · score 77

Install: claude install-skill tboome33/obsidian-mcp-router

# wiki-tour Build a **guided tour** through a vault: an ordered sequence of steps that teaches the vault's structure in a sensible reading order, derived from the **knowledge graph's link topology** (fan-in/backlinks, entry points, catalog.md sections). Reference: [[understand-anything-roadmap]] item #3. Same split as `/wiki-graph`: the **topology + step ordering is deterministic** (the `build_wiki_tour` tool); **you (Claude) write the pedagogical narrative** — the *why* of each step. ## Pre-condition The knowledge graph must exist: `wiki-meta/graph/knowledge-graph.json`. If it doesn't, run `/wiki-graph` first (the tool will tell you). Richer tours come from a richer graph — suggest `/wiki-refresh-digests` + `/wiki-graph` if the vault has few digests. ## Steps ### 1. Resolve scope - No arg → whole-vault tour. - `scope` arg → one section/topic (by catalog.md heading) or a path substring. For a multi-project vault, tour one project at a time (e.g. `/wiki-tour Dedibox`). If unsure which scopes exist, read `wiki-meta/catalog.md` section headings and offer a menu. ### 2. Compute the deterministic skeleton ``` mcp__obsidian-router__build_wiki_tour({ vault, scope?, maxSteps? }) ``` Returns: ordered `steps[]` — each with `order`, a default `title`, and `nodes[]` (`{id, name, summary}`) — plus `entryPoints[]` and `totalArticles`. The skeleton is: an **overview step** (the entry points — highest fan-in, boosted for index/MOC names) then **one step per catalog.md section** (it