Skip to main content
skill CX Codex

wiki-mode — Claude Code skill: what it does, how to install

wiki-mode configures vault filing methodologies like PARA, LYT, or Zettelkasten and suggests destinations for new Obsidian notes without writing files.

MIT 344 installs ★ 16,676 updated 2026-10-22

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add AgriciDaniel/claude-obsidian --skill wiki-mode -a claude-code
Open on GitHub

What wiki-mode does

This skill guides assistants on where to place new knowledge items inside an Obsidian vault. It routes notes according to Generic, LYT, PARA, or Zettelkasten conventions. The helper only prints destination suggestions and sanitizes paths. It will not write note contents, migrate existing files, or bulk-create directory trees.

Under the hood, the skill relies on Python 3 and two scripts from the package root: claude-obsidian.py and wiki-mode.py. Vault settings live in .vault-meta/mode.json. If this file is corrupt, the tool fails closed instead of silently falling back to defaults. Changing methodologies requires a two-step transaction with an explicit plan preview and SHA256 approval.

What it helps with

  • Route new notes according to PARA, LYT, or Zettelkasten structures
  • Detect the active filing methodology in an Obsidian vault
  • Switch vault mode using a previewed SHA256 transaction
  • Prevent broken note structures by validating .vault-meta/mode.json

Example prompts for the agent

  • What is the current filing mode of my Obsidian vault?
  • Suggest a folder for a note on distributed caching under PARA
  • Switch my vault methodology to Zettelkasten

How to install wiki-mode

1Skills CLI (Vercel)

npx skills add AgriciDaniel/claude-obsidian --skill wiki-mode -a claude-code

2Manually: put the files in place

~/.claude/skills/wiki-mode/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/wiki-mode/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about wiki-mode

How to install wiki-mode in Claude Code?

Run npx skills add AgriciDaniel/claude-obsidian --skill wiki-mode -a claude-code.

What does wiki-mode do?

It reads .vault-meta/mode.json and suggests target directories for incoming notes based on Generic, LYT, PARA, or Zettelkasten rules. It does not create or edit notes directly.

What dependencies does wiki-mode require?

It needs Python 3 and the scripts claude-obsidian.py and wiki-mode.py present at the installed package root.

Source text

SKILL.md · MIT
---
name: wiki-mode
description: "Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing. This skill does not save content or migrate notes."
---

# Route by vault methodology

This skill returns filing suggestions. It does not write knowledge pages or
move existing notes. If `.vault-meta/mode.json` is absent, use `generic`. If
the file exists but is invalid, fail closed and repair it through a reviewed
configuration operation before suggesting routes; never silently substitute
Generic for corrupt user configuration.

Resolve the installed product root from this skill's own location, not from the
vault or current working directory:

```bash
PRODUCT_ROOT=/absolute/path/to/installed/claude-obsidian
CORE="$PRODUCT_ROOT/scripts/claude-obsidian.py"
MODE_HELPER="$PRODUCT_ROOT/scripts/wiki-mode.py"
test -f "$CORE" && test -f "$MODE_HELPER"
```

Every `../wiki/references/` link in this file resolves the same way, relative
to this skill's own directory under `$PRODUCT_ROOT`, never relative to the
selected vault's `wiki/` directory.

## Read and route safely

Always select the vault explicitly:

```bash
python3 "$MODE_HELPER" --vault "$VAULT" get
python3 "$MODE_HELPER" --vault "$VAULT" config
python3 "$MODE_HELPER" --vault "$VAULT" route concept "Concept name"
python3 "$MODE_HELPER" --vault "$VAULT" route source "Source title"
```

The helper validates the selected vault, confines paths, sanitizes names, and
prints a suggestion only. A calling skill may override the suggestion when the
user supplies a more specific project, area, MOC, or parent note, but it must
still apply its eventual writes through one operation transaction.

| Mode | Routing intent |
|---|---|
| `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. |
| `zettelkasten` | Flat atomic notes with time-sortable, collision-resistant identifiers and explicit links. |

Use the templates as structural guidance: [LYT atomic](templates/lyt/atomic-template.md),
[LYT MOC](templates/lyt/moc-template.md), [PARA area](templates/para/area-template.md),
[PARA project](templates/para/project-template.md),
[PARA resource](templates/para/resource-template.md), or
[Zettelkasten atomic](templates/zettel/atomic-template.md). They use canonical
`type` values from `claude_obsidian/page_schema.py` and a separate flat
`methodology_role` property:

| Template | Type | Methodology role |
|---|---|---|
| LYT atomic | `concept` | `atomic` |
| LYT MOC | `meta` | `moc` |
| PARA area | `concept` | `area` |
| PARA project | `entity` | `project` |
| PARA resource collection | `concept` | `resource` |
| Zettelkasten atomic | `concept` | `zettel` |

A resource template describes a topic collection. Use `source` instead when the
new page represents a particular captured source. The methodology role does not
add a router type: pass the canonical type and respect the chosen project, area,
or MOC destination. Structural MOCs use an explicit destination; `meta` is not a
routable new-note type. Existing user pages, custom type vocabularies, and saved
Dataview queries remain unchanged. Any requested migration needs its own reviewed
plan; switching mode never rewrites existing notes.

## Change mode

A mode change is one configuration operation, dry-run first:

1. Read the current `.vault-meta/mode.json`, or start from the helper's default
   config when it is absent.
2. Validate the requested mode as exactly `generic`, `lyt`, `para`, or
   `zettelkasten`. Preserve the other mode-specific settings.
3. Choose and retain a pinned UTC timestamp and operation ID for both commands.
4. Preview the canonical configuration transaction; the command records the
   current target hash and limits the write to `.vault-meta/mode.json`:

   ```bash
   python3 "$CORE" mode set "$MODE" --vault "$VAULT" \
     --generated-at "$GENERATED_AT" --operation-id "$OPERATION_ID"
   ```

5. Show the old mode, new mode, exact changed path, and complete preview. Copy
   its `approved_plan_sha256` only after review.
6. Apply by regenerating that exact vault-bound plan:

   ```bash
   python3 "$CORE" mode set "$MODE" --vault "$VAULT" \
     --generated-at "$GENERATED_AT" --operation-id "$OPERATION_ID" \
     --approved-plan-sha256 "$APPROVAL_SHA256" --apply
   ```

Follow the [operation transaction contract](../wiki/references/operation-transactions.md).
Do not use `scripts/wiki-mode.py`'s legacy direct-write `set` action or a setup
script to bypass this workflow.

Changing mode affects routing for future operations only. Never bulk-create
folders, move notes, rewrite wikilinks, or migrate existing pages as a side
effect. If migration is later requested, plan and review it as a distinct
operation with its own hashes and transaction.

## Checkpoint

Observe the user's current structure, think about how they retrieve and act on
notes, verify a few proposed routes before changing configuration, and grow by
revisiting the mode only when real filing friction appears.

© AgriciDaniel · MIT · AgriciDaniel/claude-obsidian

Similar skills

All skills for Notes, tasks and projects →

From the same set15

The whole set →
wiki-query wiki-query is a Claude Code skill that answers questions from a chosen Obsidian vault without changing its files. It uses the vault as the evidence source. CX Codex +1 512installs wiki-lint wiki-lint runs a deterministic read-only check on an Obsidian vault: dead links, orphan pages, frontmatter gaps. It reports, it does not repair. CX Codex +1 508installs canvas Creates and edits Obsidian boards in JSON Canvas format: text cards, files, links, groups and edges. Useful when you want a visual map of a vault. CX Codex +1 500installs defuddle Plans Defuddle extraction and retains already available local source files. No network cleaning ships with it — just the plan and the capture. CX Codex +1 478installs wiki-fold wiki-fold is a Claude Code skill that builds a rollup from entries in an Obsidian wiki/log.md. It previews the draft first and leaves child pages untouched. CX Codex +1 445installs wiki-retrieve wiki-retrieve builds a local BM25 index from wiki/ notes and finds relevant passages. Use it when an agent needs matching pages to read before answering a question. CX Codex +1 348installs wiki-cli wiki-cli is a Claude Code skill that checks whether the official Obsidian CLI can read a vault, then searches notes; if unavailable, it reads files directly. CX Codex +1 341installs think Applies a ten-stage OBSERVE–LISTEN–THINK–CONNECT–FEEL–ACCEPT–CREATE–GROW cycle to complex decisions, architecture reviews, and incident postmortems. Separates facts from assumptions and surfaces hidden risks. CX Codex +1 337installs

Project sponsors

Companies that keep this analytics open