/wiki

description: "LLM wiki knowledge base — understands natural language. Say what you want (use a personal specialist method, edit an external resource through a registered adapter, capture or shape an Idea, add a URL, collect a catalog, track inventory, ask a question, research, audit, or resume work) and it routes to the right workflow. Also handles init, status, and config."
argument-hint: "[<natural language request>] [init <topic-name> [--local]] [config hub-path [<path>]] [--wiki <name>]"
allowed-tools: Read, Write, Edit, Glob, Bash(ls:*), Bash(wc:*), Bash(mkdir:*), Bash(date:*), Bash(mv:*)

Your task

**Resolve the wiki.** Do NOT search the filesystem or read reference files — follow these steps: 1. Read `$HOME/.config/llm-wiki/config.json`. If it has `hub_path`, expand leading `~` only (not tildes in `com~apple~CloudDocs`) and prefer that path; use `resolved_path` only as a fallback cache when the expanded `hub_path` is unavailable and `resolved_path` is initialized. If config has only `resolved_path`, use it. If the configured path can be statted but reading `wikis.json` or listing `topics/` fails with `Operation not permitted`, stop and ask the user to grant Full Disk Access/iCloud Drive access to the launcher; do not fall back to `~/wiki` or `resolved_path`. Do not write machine-specific `resolved_path` into shared configs. 2. If no config → read `$HOME/wiki/_index.md`. If it exists → HUB = `$HOME/wiki`. If nothing found, ask the user where to create the wiki. 3. **Wiki location** (first match): `--local` → `.wiki/` in CWD; `--wiki <name>` → `HUB/wikis.json` lookup with portable path resolution (`<HUB>`, `~`, absolute, or HUB-relative); if the registry path is stale, fall back to `HUB/topics/<name>`; CWD has `.wiki/` → use it; else → HUB. 4. Read `<wiki>/_index.md` if found. Variant: **wiki-neutral** — `wiki.md` is the router, init, and config command, so "wiki missing" is not always an error; the init subcommand creates the wiki, status shows an empty hub gracefully, and the natural-language router explains how to create one.

You are the llm-wiki knowledge base manager. Read the skill at `skills/wiki-manager/SKILL.md` and structure reference at `skills/wiki-manager/references/wiki-structure.md` for full conventions.

---

If $ARGUMENTS contains "init"

Initialize a new wiki. Parse arguments:

• `init <name>` → create topic wiki at `HUB/topics/<name>/`
• `init <name> --local` → create local wiki at `.wiki/` in current project
• `init` (no name) → ask: "What topic is this for?" Then create the topic wiki with their answer.

**A topic name is always required.** There is no bare global wiki — HUB is only a hub (wikis.json + _index.md + log.md). All content lives in topic sub-wikis.

**Steps:**

1. If HUB doesn't exist yet, create the hub first:

• `HUB/wikis.json` (empty registry)
• `HUB/_index.md` (hub index with empty topic wiki table)
• `HUB/log.md` (global activity log)
• `HUB/topics/` directory
• NO `raw/`, `wiki/`, `inventory/`, `datasets/`, `output/`, `inbox/`, `config.md`, or `.obsidian/` at the hub level.

2. Create the core topic wiki directory structure:

• `inbox/`, `inbox/.processed/`
• `raw/`, `raw/articles/`, `raw/papers/`, `raw/repos/`, `raw/notes/`, `raw/data/`
• `wiki/`, `wiki/concepts/`, `wiki/topics/`, `wiki/references/`, `wiki/theses/`
• `output/`
• Do not create `inventory/` or `datasets/` during init. Those layers are

created lazily by `/wiki:inventory`, `/wiki:dataset`, or lint when a partially existing layer needs repair.

• For local wikis (`--local`): append `.wiki/` to the project's `.gitignore`.

3. Create `.obsidian/` directory with minimal vault config:

• `.obsidian/app.json`:

     {
       "showFrontmatter": true,
       "alwaysUpdateLinks": true,
       "newLinkFormat": "relative",
       "useMarkdownLinks": false
     }

• `.obsidian/appearance.json`:

     {
       "accentColor": ""
     }

• `.obsidian/graph.json`:

     {
       "collapse-filter": false,
       "search": "",
       "showTags": true,
       "showAttachments": false,
       "showOrphans": true,
       "collapse-color-groups": false,
       "collapse-display": false,
       "showArrow": true,
       "textFadeMultiplier": 0,
       "nodeSizeMultiplier": 1,
       "lineSizeMultiplier": 1
     }

4. Create empty `_index.md` only in the directories created during init, following the format in `references/wiki-structure.md`. Use today's date. Set all counts to 0. Do not write empty indexes for optional layers that do not exist yet.

5. Create `log.md` with initial entry:

   # Wiki Activity Log

   ## [YYYY-MM-DD] init | Wiki initialized

6. Ask the user: "What is this wiki about?" Use their answer to create `config.md` with title, description, scope, and today's date. Also create a starter `schema.md` in `schema_state: advisory` with a small default vocabulary; it is human-owned and can be trimmed later.

7. Before registering, check both `HUB/topics/<slug>/` and `HUB/topics/.archive/<slug>/`, plus any `wikis.json` entry with that slug. If an archived topic already exists, stop and ask whether to restore it with `/wiki:archive restore <slug>` or choose a different slug. Do not silently create a new active topic over an archived topic boundary.

8. Register in `HUB/wikis.json` with a portable relative path (`topics/<slug>`) and update hub `_index.md` topic wiki table. For local wikis, add to the `local_wikis` array with its absolute local path.

9. Report what was created and suggest:

• `/wiki:research "topic" --sources 10` — auto-research to bootstrap
• `/wiki:ingest <url|file|text>` — add source material
• `/wiki:ingest-collection <repo|wiki-dump>` — bulk import a bounded upstream collection
• `/wiki:adapter list` — inspect explicitly registered local private adapters
• `/wiki:collect "<things>"` — find,