wiki-maintainer

Maintain memory wiki vaults with deterministic, source-backed page updates.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/vut08905/openclaw-app --skill wiki-maintainer-vut08905
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-maintainer
Source: https://github.com/vut08905/openclaw-app/tree/main/extensions/memory-wiki/skills/wiki-maintainer
Command: npx skills add https://github.com/vut08905/openclaw-app --skill wiki-maintainer-vut08905

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Memory-wiki maintenance often suffers from drift and missing provenance. This skill provides deterministic, source-backed workflows to keep memory pages stable and auditable.

Core Features & Use Cases

  • wiki_status to understand vault mode, path, and Obsidian CLI availability.
  • memory_search with corpus=all to perform a comprehensive recall across durable memory and the compiled wiki.
  • wiki_search and wiki_get to locate and inspect candidate pages before editing.
  • wiki_apply for targeted synthesis and metadata updates.
  • wiki_lint to surface contradictions, provenance gaps, and open questions after meaningful wiki edits.
  • wiki ingest, wiki compile, and wiki lint workflows; bridge/import features for public memory artifacts.
  • In bridge mode, run wiki bridge import before relying on search results if you need the latest public memory artifacts pulled in.
  • In unsafe-local mode, optionally import from private local paths when explicitly opted in.
  • Keep generated sections inside managed markers and avoid overwriting human note blocks.
  • Preserve page identity and avoid duplicates by updating existing entities.
  • Preserve Obsidian-friendly wikilinks when the vault render mode is obsidian.

Quick Start

Run the wiki maintainer tool to refresh memory wiki pages from the vault.

Frequently Asked Questions about wiki-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain a memory wiki vault without losing source provenance?

To maintain a memory wiki vault with source provenance, use deterministic workflows that apply source-backed updates to stable pages. This approach enforces safe mutations with managed markers, ensuring generated sections stay isolated and human note blocks remain untouched.

What is the best way to surface contradictions and provenance gaps in a knowledge vault?

The best way to surface contradictions and provenance gaps in a knowledge vault is to run a linting command after meaningful wiki edits. This process audits recent changes to identify missing source provenance, logical conflicts, and unresolved open questions.

How do I perform a comprehensive recall across durable memory and a compiled wiki?

To perform a comprehensive recall across durable memory and a compiled wiki, execute a memory search with the corpus parameter set to all. This queries both the durable memory sources and the compiled wiki pages simultaneously.

Does wiki maintenance work with Obsidian vaults and wikilinks?

Yes, wiki maintenance works with Obsidian vaults by checking Obsidian CLI availability and preserving Obsidian-friendly wikilinks. When the vault render mode is set to obsidian, the system ensures formatting aligns with Obsidian standards.

How do I import public memory artifacts into a wiki during bridge mode?

To import public memory artifacts into a wiki during bridge mode, run the bridge import workflow before relying on search results. This pulls the latest public memory artifacts into the vault to ensure updates are synthesized from current data.

Can I import from private local paths when updating memory wiki pages?

Yes, you can import from private local paths when updating memory wiki pages by explicitly opting into unsafe-local mode. This allows the bridge import workflow to access local directories when public artifacts are insufficient for the synthesis workflow.