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 maintenance workflow for 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, wiki_get, and memory_search with corpus=all to understand vault mode and recall across durable memory plus the compiled wiki. - Deterministic Maintenance Loop: Run openclaw wiki ingest, compile, and lint as the default cycle, with bridge or unsafe-local import modes for pulling in external or private artifacts. - Safe Editing Discipline: Keep generated sections inside managed markers, preserve human note blocks, maintain stable page identity, and retain Obsidian wikilinks when the vault renders in Obsidian mode. - Use Case: After a week of new memory artifacts, run the ingest-compile-lint loop, search for candidate pages, update existing entities with wiki_apply, and lint to surface contradictions and provenance gaps before trusting the vault. ## Quick Start Ask the assistant to check the wiki vault status, ingest and compile the latest memory artifacts, then lint the vault and report any contradictions or provenance gaps.
