wiki-maintainer

To maintain an OpenClaw memory wiki, this skill enforces deterministic workflows and source-backed edits across all vault pages. It coordinates updates across pages, managed blocks, and citations to keep the memory vault consistent and auditable.

Provenance-managed wiki editing tracks the source backing each update applied to the memory vault. This skill applies safety checks and runs openclaw wiki ingest/compile/lint cycles to ensure provenance and consistency across all wiki pages.

You start a memory wiki maintenance cycle by checking wiki_status for vault mode and path availability, then use wiki_search and wiki_get to locate candidate pages. The workflow applies and lints updates through the OpenClaw CLI for safe vault curation.

Yes, the wiki-maintainer checks wiki_status to understand Obsidian CLI availability for memory vault curation. It integrates with the OpenClaw CLI to apply deterministic page generation and source-backed edits within your existing Obsidian workflow.

Memory wiki vaults lose consistency when updates lack deterministic enforcement and provenance tracking. This skill solves the problem by applying source-backed edits, managed blocks, and running openclaw wiki lint to ensure all coordinated page updates remain auditable.

The best way to cross-reference memory vault pages during wiki maintenance is using memory_search for cross-dedicated recall. This skill leverages memory_search alongside wiki_search and wiki_get to identify candidate pages before applying deterministic, source-backed updates.