Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.
复制下面这句话,粘贴给 Claude Code、Codex、Cursor 等 AI 编程工具,它会读取安装说明并在你确认后完成安装。
请阅读 https://ai.atlankj.com/install/asset/gh-wiki-maintainer-7ddb4dc9ef4d ,按照其中的说明把「wiki-maintainer」安装到你(当前 AI 工具)中。执行前先告诉我将运行的命令和写入的位置,等我确认。
查看 AI 将读取的安装说明正在读取 GitHub 原文…
内容来自 GitHub 原始文件,由原作者维护。在 GitHub 查看
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. Verify contact data before use; generated people facts need source-class provenance.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.