wiki-asklisted

> Engine invocation — resolve it ONCE, in this order, and use the first that exists: > 1. `bun "<plugin-root>/src/cli.ts"`, where `<plugin-root>` is the directory TWO levels above > this skill's base directory (skills/<name>/ → plugin root). This is the plugin and clone > install — the normal case. Stop here when that file exists. > 2. `bun "$LLMWIKI_ROOT/src/cli.ts"` when `LLMWIKI_ROOT` is set — a host that copied this > skill folder OUT of the plugin (OpenClaw, Hermes, `skills add`) leaves step 1 pointing at > that host's skills directory, not at an engine. > 3. `llmwiki` on PATH — the launcher `setup.sh` writes to `~/.local/bin`, or the npm bin. > > If none of the three resolve, say so once and stop. Do NOT guess a path: the engine writes > into a repository, and a guessed root writes into the wrong one. Every `llmwiki …` or > engine-CLI reference below means the invocation you resolved here. # /wiki-ask — Compounding Loop query loop (local engine v2) - **Custom conventions**: if a team `llmwiki.config.toml` (or a per-repo `configs/*.toml`) is active (check: `llmwiki config <repo>` shows a non-default source), run `llmwiki conventions <repo>` FIRST and follow ITS category table (dirs · domains · review gates) over any category names written below. **Ask** this repo's (`$CLAUDE_PROJECT_DIR`) accumulated wiki (`docs/wiki/`), synthesize an answer with citations, then **file it back as a new wiki page** if it has value ("explorations should compound"). Engine =