geronimo-iia/llm-wiki-skills/config

Config

Two configuration files control llm-wiki behavior:

• ~/.llm-wiki/config.toml — global engine config (local to the

machine, never committed). Override the path with --config <path> or the LLM_WIKI_CONFIG environment variable.

• <wiki>/wiki.toml — per-wiki config (committed to git, shared)

Config file location

1. --config <path> CLI flag        (highest)
2. LLM_WIKI_CONFIG env var
3. ~/.llm-wiki/config.toml         (default)

The --config flag is global — it works on every subcommand including serve. Use it in .mcp.json to run isolated environments:

{
  "llm-wiki": {
    "command": "llm-wiki",
    "args": ["--config", "/path/to/config.toml", "serve"]
  }
}

Or via env:

{
  "llm-wiki": {
    "command": "llm-wiki",
    "args": ["serve"],
    "env": { "LLM_WIKI_CONFIG": "/path/to/config.toml" }
  }
}

Resolution order (settings within the config)

1. CLI flag / MCP parameter
2. Per-wiki config   (wiki.toml)
3. Global config     (config.toml)
4. Built-in default

Per-wiki wins over global. CLI flags win over everything.

wiki.toml

Lives at the wiki repository root. Contains wiki identity and optional per-wiki overrides.

name        = "research"
description = "ML research knowledge base"
 
[ingest]
auto_commit = true
 
[validation]
type_strictness = "loose"

Type overrides ([types.*]) are also declared here but managed through the schema skill.

List current config

wiki_config(action: "list")

Returns all resolved config values for the default wiki.

{
  "defaults.search_top_k": 10,
  "defaults.page_mode": "flat",
  "ingest.auto_commit": true,
  "validation.type_strictness": "loose"
}

Read a config value

wiki_config(action: "get", key: "defaults.search_top_k")

Set a config value

Per-wiki (writes to wiki.toml):

wiki_config(action: "set", key: "ingest.auto_commit", value: "false")

Global (writes to config.toml):

wiki_config(action: "set", key: "defaults.search_top_k", value: "15", global: true)

Global-only keys reject per-wiki writes with an error.

Overridable settings

These keys can appear in both config.toml and wiki.toml.

Search status weights

Control how much each status value contributes to search ranking. Higher weight = pages with that status rank higher in results.

wiki_config(action: "set", key: "search.status.active", value: "1.2")
wiki_config(action: "set", key: "search.status.draft", value: "0.3")
wiki_config(action: "set", key: "search.status.archived", value: "0.1")

Custom status values defined in your schemas work the same way:

wiki_config(action: "set", key: "search.status.accepted", value: "1.5")

Per-wiki overrides take precedence over global values — use them when a wiki has a domain-specific status taxonomy (e.g. ADR accepted/superseded).

Global-only settings

These keys can only appear in config.toml. Setting them in wiki.toml is rejected.