wiki-mode
wiki-mode lets you pick an organizational methodology—LYT, PARA, Zettelkasten, or Generic—and store it in `.vault-meta/mode.json` so wiki-ingest, save, and autoresearch route new pages consistently. Set your mode once with an interactive setup script; switching modes later only affects newly-filed pages. Each methodology ships with templates and folder conventions tailored to its philosophy.
wiki-mode lets you declare an organizational methodology (LYT, PARA, Zettelkasten, or Generic) that guides how new pages file across your vault.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-05-28
wiki-mode lets you declare an organizational methodology (LYT, PARA, Zettelkasten, or Generic) that guides how new pages file across your vault. wiki-mode lets you pick an organizational methodology—LYT, PARA, Zettelkasten, or Generic—and store it in `.vault-meta/mode.json` so wiki-ingest, save, and autoresearch route new pages consistently. Set your mode once with an interactive setup script; switching modes later only affects newly-filed pages. Each methodology ships with templates and folder conventions tailored to its philosophy.
Use it when
- wiki-mode supports four filing conventions.
- wiki-mode's setup script lets you declare LYT as your vault methodology.
Verify before relying
Read SKILL.md below before installing (7 files). Open directory: indexed for reading, not audited.
Install
AgriciDaniel/claude-obsidian/wiki-mode · 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
How do I organize my Obsidian vault with wiki-mode?
wiki-mode lets you pick an organizational methodology—LYT, PARA, Zettelkasten, or Generic—and store it in `.vault-meta/mode.json` so wiki-ingest, save, and autoresearch route new pages consistently. Run the interactive setup script once to declare your chosen methodology, and wiki-mode will apply its folder conventions and templates automatically to all newly-filed pages.
What's the difference between LYT, PARA, and Zettelkasten in wiki-mode?
wiki-mode supports four filing conventions. LYT (Linking Your Thinking) emphasizes Maps of Content and bidirectional linking. PARA (Projects, Areas, Resources, Archive) organizes by life domains and project status. Zettelkasten uses ID-based atomic notes with structured linking. Generic provides a flexible baseline. Each ships with methodology-specific templates and folder structures tailored to its philosophy.
How do I set up LYT linking your thinking in wiki-mode?
wiki-mode's setup script lets you declare LYT as your vault methodology. Once configured, wiki-mode stores this choice in `.vault-meta/mode.json`. New pages then route to LYT-aligned folders, and you gain access to LYT templates including Maps of Content (MOC) structures and bidirectional linking patterns that wiki-ingest and autoresearch will apply consistently.
Can I switch my vault organization mode later, and what happens?
Yes. wiki-mode lets you switch between LYT, PARA, Zettelkasten, and Generic at any time by updating `.vault-meta/mode.json` or re-running the setup script. Switching modes only affects newly-filed pages going forward; existing notes remain untouched. This lets you experiment with different methodologies without disrupting your current vault.
What vault mode am I currently using with wiki-mode?
wiki-mode stores your active methodology in `.vault-meta/mode.json`. Check that file to see whether you're running LYT, PARA, Zettelkasten, or Generic mode. This configuration tells wiki-ingest, save, and autoresearch which folder structure and templates to apply when routing and creating new pages.
How does wiki-mode route new pages to the correct folder structure?
wiki-mode reads your declared methodology from `.vault-meta/mode.json` and uses it to guide wiki-ingest, save, and autoresearch. Each methodology has its own folder conventions—LYT uses MOC hierarchies, PARA uses project/area/resource/archive buckets, Zettelkasten uses ID-based filing. New pages automatically route to the correct folders based on your active mode.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
wiki-mode: Methodology Modes for the Compound Vault
The v1.6 + v1.7 vault structure was opinion-free — wiki/sources/, wiki/entities/, wiki/concepts/, and so on. That works for power-users with their own organizational instincts. It does NOT serve the large segment of Obsidian users who want a named methodology to follow.
v1.8 ships wiki-mode to close that gap. A vault declares a mode (LYT, PARA, Zettelkasten, or Generic) in .vault-meta/mode.json; the other skills consult it before deciding where to file new pages.
(truncated - see the full file via the links below)
File tree — 7 files
skills/wiki-mode/SKILL.md
skills/wiki-mode/templates/lyt/atomic-template.md
skills/wiki-mode/templates/lyt/moc-template.md
skills/wiki-mode/templates/para/area-template.md
skills/wiki-mode/templates/para/project-template.md
skills/wiki-mode/templates/para/resource-template.md
skills/wiki-mode/templates/zettel/atomic-template.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 › “Declare and configure a named organizational methodology for the vault”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
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.
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.
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-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.
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.
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.
More skills obsidian-bases (MIT) · wiki (MIT)