What does this skill do, and when should you use it?
wiki-mode is an Agent Skill in the claude-obsidian repository for selecting and reading an organizational methodology for a Compound Vault. It supports LYT, PARA, Zettelkasten, and Generic modes, storing the selection in `.vault-meta/mode.json`. Related skills consult that configuration when filing source, entity, concept, session, and research pages. Generic is the default and preserves the v1.6/v1.7 behavior.
Reads .vault-meta/mode.json and falls back to generic when it is absent; uses bash bin/setup-mode.sh to configure or switch modes; returns mode-specific safe filing paths for each content type; provides folder, filename, frontmatter, and template conventions for LYT, PARA, and Zettelkasten; and supplies routing information consumed by wiki-ingest, save, and autoresearch.
- Obsidian users with knowledge bases of more than 100 notes who want MOCs and flat atomic notes can use LYT.
- Knowledge workers managing projects and ongoing responsibilities by actionability can use PARA.
- Researchers and long-term thinkers who need unique IDs, atomic claims, and dense bidirectional links can use Zettelkasten.
- Users migrating from v1.7 or avoiding an opinionated structure can keep the Generic mode.
How do you install this skill?
- Back up the vault and manually inspect .vault-meta/mode.json before switching; existing files are not migrated, so old and new directory structures may coexist.
- Review the actual implementations of setup-mode.sh, wiki-mode.py, and the three consumers to confirm mode validation, path sanitization, write-failure handling, and permission boundaries.
- No Chinese trigger phrases or Chinese output examples are supplied; Chinese users should verify reliable semantic invocation.
- Shell / CLI
- Local filesystem
BashPython 3
The skill is distributed with the 15-skill AgriciDaniel/claude-obsidian collection. Clone the repository as an Obsidian vault with git clone https://github.com/AgriciDaniel/claude-obsidian, enter the directory, and run bash bin/setup-vault.sh. wiki-mode requires no separate setup script; run bash bin/setup-mode.sh only when explicitly configuring a non-default mode.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/AgriciDaniel/claude-obsidian.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/wiki-mode" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- set vault mode,
- switch to PARA,
- what's my vault mode,
From the vault root, run bash bin/setup-mode.sh and choose LYT, PARA, Zettelkasten, or Generic. It also responds to triggers such as “set vault mode,” “switch to PARA,” “use LYT,” “what's my vault mode,” and “zettelkasten setup.” Switching affects newly filed pages only; existing files are not migrated automatically.
What are this skill's strengths and limitations?
- Offers four explicit organizational choices: LYT, PARA, Zettelkasten, and Generic.
- Centralizes the choice in `.vault-meta/mode.json` for three filing-related skills to consume.
- Keeps Generic as the default, preserving the earlier vault structure.
- Includes mode-specific templates and concrete folder, naming, and frontmatter conventions.
- It handles configuration and routing; actual page filing depends on sibling skills such as `wiki-ingest`, `save`, or `autoresearch`.
- Changing modes does not automatically migrate existing files.
- The setup flow depends on Bash scripts and local filesystem access; no standalone installation procedure is documented for this skill.
- Zettelkasten requires more discipline, including timestamp-based IDs, atomic notes, and parent/child ID metadata.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Compound Vault Methodology Modes this page | 56 · Use with care | ★ 16k | 1mo ago | MIT |
| Wiki Knowledge Companion | 49 · Use with care | ★ 16k | 1mo ago | MIT |
| Autonomous Research Filing | 52 · Use with care | ★ 16k | 1mo ago | MIT |
| LLM Wiki Manager | 51 · Use with care | ★ 71 | 1mo ago | MIT |
| Wiki Log Folder | 55 · Use with care | ★ 16k | 1mo ago | MIT |
The README compares this methodology system with Ideaverse Pro 2.0, describing that product as an opinionated LYT structure while claude-obsidian also provides PARA, Zettelkasten, and mode-aware routing. Its comparison table lists no equivalent first-class methodology modes for Smart Connections or Copilot. The practical choice is whether you need Claude Code-driven routing in a local Markdown vault.
How did FollowSkills review this skill?
The skill declares only Read, Write, and Bash, and its core behavior is limited to reading or writing .vault-meta/mode.json; setup is interactive, and mode changes explicitly avoid automatic migration, reducing accidental deletion and data-loss risk. Points are deducted because Bash is broad, while this skill does not show input validation, write confirmation, rollback, sensitive-data handling, or a complete data-flow disclosure.
The four modes, directory conventions, schema, consumer integration, and migration behavior are internally consistent; repository CI also invokes the wiki-mode CLI surfaces get/config/id/templates. Points are deducted because this review is static, the key paths were not executed, the implementations of setup-mode.sh, wiki-mode.py, and the three consumers are absent, and abnormal-input, corrupted-config, and failure-feedback coverage is limited.
The skill clearly states four modes, use cases, generic defaults, switching behavior, and migration boundaries; its core function is local Markdown and JSON rather than dependence on an unreachable overseas service. Points are deducted because exclusion conditions for semantic triggering, Chinese-language examples or behavior, and non-fit boundaries for small vaults, mixed modes, and custom routing are not sufficiently specified.
The skill provides a clear four-mode structure, schema, routing table, templates, migration guidance, and cross-references; the README, MIT license, security policy, version references, and CI provide repository-level maintenance signals. Points are deducted because the selected skill has no independent version, changelog, named maintenance responsibility, or update path, and the key external documents and consumer contracts were not supplied as skill evidence.
For configuring or explaining vault methodology, the skill supplies directly usable directory conventions, configuration format, and templates, and clearly states that existing files are not migrated automatically. Points are deducted because actual routing depends on other unsupplied skills and scripts, templates are advisory, and there is no representative output or end-to-end execution evidence; users may still need manual migration and link/MOC maintenance.
A real CI workflow is supplied and explicitly exercises wiki-mode CLI surfaces; the repository also contains committed tests for other scripts. Points are deducted because there is no skill-specific test source, third-party corroboration, or independently reproduced result. Static review cannot confirm full implementation-documentation alignment, so the score remains at the static ceiling.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →