wiki-maintainer
Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.
npx skills add Health-Yang/MineEcho --skill wiki-maintainer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Use this skill when working inside a memory-wiki vault. - Prefer `wiki_status` first when you need to understand the vault mode, path, or Obsidian CLI availability. - Prefer `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. - Use `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. - Use `wiki_apply` for narrow synthesis filing and metadata updates when a tool-level mutation is enough. - Run `wiki_lint` after meaningful wiki updates so contradictions, provenance gaps, and open questions get surfaced before you trust the vault. - Use `openclaw wiki ingest`, `openclaw wiki compile`, and `openclaw wiki lint` as the default maintenance loop. - In `bridge` mode, run `openclaw wiki bridge import` before relying on search results if you need the latest public memory artifacts pulled in. - In `unsafe-local` mode, use `openclaw wiki unsafe-local import` only when the user explicitly opted into private local path access. - Keep generated sections inside managed markers. Do not overwrit
What does the wiki-maintainer skill do?
Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.
How do I install it?
Run `npx skills add Health-Yang/MineEcho --skill wiki-maintainer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Health-Yang/MineEcho, a repository with 248 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.