Wiki mode

Skill aidehua08/codex-obsdian/plugins/codex-obsdian/skills/wiki-mode

Codex-native full core port of claude-obsidian: Obsidian wiki memory, source ingest, hybrid retrieval, locks, DragonScale utilities, canvas, lint, fold, and skills.

Install

npx -y skills add aidehua08/codex-obsdian --skill wiki-mode

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

3.9 KB, 830 tokens by cl100k_base, as published. Nobody here has run it

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:

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"

Read and route safely

Always select the vault explicitly:

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 under templates/ as structural guidance, not authority to overwrite user conventions.

Change mode

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

Read the current .vault-meta/mode.json, or start from the helper's default config when it is absent.
Validate the requested mode as exactly generic, lyt, para, or zettelkasten. Preserve the other mode-specific settings.
Choose and retain a pinned UTC timestamp and operation ID for both commands.
Preview the canonical configuration transaction; the command records the current target hash and limits the write to .vault-meta/mode.json:
```
python3 "$CORE" mode set "$MODE" --vault "$VAULT" \
  --generated-at "$GENERATED_AT" --operation-id "$OPERATION_ID"
```
Show the old mode, new mode, exact changed path, and complete preview. Copy its approved_plan_sha256 only after review.

Apply by regenerating that exact vault-bound plan:

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. 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.

Gives 0 of the 12 instructions most note taking skills give in 830 tokens

Counted across 686 of the 876 authors here whose files we hold, read 2026-08-07

include a visual element on every slidein 44 of 686, across 13 files
use wikilinks for internal vault linksin 36 of 686, across 12 files
commit to a single visual motif across every slidein 34 of 686, across 9 files
use subagents to visually inspect rendered slidesin 31 of 686, across 7 files
read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
keep 0.5 inch minimum marginsin 30 of 686, across 7 files
re-verify affected slides after every fixin 27 of 686, across 5 files
run content QA checks before declaring successin 26 of 686, across 3 files
Use Markdown links for external URLs onlyin 26 of 686, across 11 files
pick a bold topic specific color palettein 24 of 686, across 2 files
read editing guide before editing existing presentationsin 23 of 686, across 1 file
use one dominant color across all slidesin 23 of 686, across 1 file

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.