Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.
Use this skill when working inside a memory-wiki vault.
wiki_status first when you need to understand the vault mode, path, or Obsidian CLI availability.memory_search with corpus=all when the shared memory tools are available and you want one recall pass across durable memory plus the compiled wiki.wiki_search to discover candidate pages when you want wiki-specific ranking/provenance, then wiki_get to inspect the exact page before editing or citing it.wiki_apply for narrow synthesis filing and metadata updates when a tool-level mutation is enough.wiki_lint after meaningful wiki updates so contradictions, provenance gaps, and open questions get surfaced before you trust the vault.openclaw wiki ingest, openclaw wiki compile, and openclaw wiki lint as the default maintenance loop.bridge mode, run openclaw wiki bridge import before relying on search results if you need the latest public memory artifacts pulled in.unsafe-local mode, use openclaw wiki unsafe-local import only when the user explicitly opted into private local path access.obsidian.