What problem does it solve? Keeping a long-lived memory wiki consistent is hard: pages drift, duplicates appear, provenance gets lost, and generated content can overwrite human notes. This Skill provides a disciplined workflow for maintaining an OpenClaw memory-wiki vault so pages stay deterministic, source-backed, and lint-clean. ## Core Features & Use Cases - Vault inspection and search: Use wiki_status, wiki_search, and wiki_get to understand vault mode, discover candidate pages, and inspect exact content before editing. - Controlled updates: Apply narrow synthesis and metadata changes with wiki_apply, keeping generated sections inside managed markers and preserving human note blocks. - Maintenance loop: Run openclaw wiki ingest, openclaw wiki compile, and openclaw wiki lint to surface contradictions, provenance gaps, and open questions. - Use Case: After a week of captured memory artifacts, run the ingest-compile-lint loop to refresh entity pages, merge duplicates, and verify every claim traces back to a raw source. ## Quick Start Ask the assistant to check the wiki vault status, search for the relevant page, apply the update, and then run the wiki lint to verify consistency.
