wiki-maintainer

Maintain the OpenClaw memory wiki vault with deterministic pages and source-backed updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates to ensure auditability and reduce drift across knowledge artifacts.

Core Features & Use Cases

  • Deterministic page generation and versioned updates to the memory wiki vault.
  • Block-level management to maintain structural consistency across pages and enable provenance notes.
  • Source-backed ingestion and update workflow to preserve traceability of changes.
  • Use cases include refreshing memory pages after experiments, consolidating related notes, and aligning pages with authoritative references.

Quick Start

Run the wiki-maintainer to initialize and apply deterministic updates to the memory wiki vault from source-backed blocks.

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 deterministic memory wiki vault with consistent page structure?▼

Maintain a deterministic memory wiki vault by applying guarded update workflows and block-level management to generate versioned pages with structural consistency, provenance, and rollback capabilities.

What is the best way to prevent data drift when updating memory wiki pages?▼

Prevent data drift by using source-backed ingestion workflows that validate updates against authoritative references, applying provenance notes and rollback capabilities to maintain page integrity.

How do I capture provenance and traceability for versioned wiki page updates?▼

Capture provenance and traceability for versioned wiki page updates through block-level management and source-backed ingestion workflows that validate changes against authoritative references.

Can I roll back changes if a memory wiki update introduces inconsistencies?▼

Yes, you can roll back changes if a memory wiki update introduces inconsistencies, because the vault implements clear rollback capabilities alongside guarded update workflows to prevent data drift.

When do I need deterministic page generation for a memory vault?▼

You need deterministic page generation for a memory vault when consolidating related notes, refreshing pages after experiments, or aligning content with authoritative references to ensure auditability and reduce drift.

Does wiki-maintainer require external dependencies to manage source-backed updates?▼

No, wiki-maintainer does not require external dependencies to manage source-backed updates, operating independently to apply guarded workflows, validate references, and maintain vault structure.