wiki-maintainer

Maintain OpenClaw memory wiki vaults with ingest, compile, and lint workflows.

4|2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/bitan-del/gods-eye --skill wiki-maintainer-bitan-del
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-maintainer
Source: https://github.com/bitan-del/gods-eye/tree/main/extensions/memory-wiki/skills/wiki-maintainer
Command: npx skills add https://github.com/bitan-del/gods-eye --skill wiki-maintainer-bitan-del

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The OpenClaw memory wiki vault requires disciplined maintenance to preserve accuracy, provenance, and navigability across many pages.

Core Features & Use Cases

  • Memory search across durable memory and the compiled wiki.
  • Deterministic maintenance loops using openclaw wiki ingest, openclaw wiki compile, and openclaw wiki lint.
  • Preserve page identity and provenance while keeping Obsidian-friendly links when applicable.

Quick Start

Run the wiki maintainer tool to begin a vault health check and apply the standard maintenance cycle.

Frequently Asked Questions about wiki-maintainer

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

FAQPage Schema
How do I maintain wiki page consistency and provenance across a memory vault?

To maintain wiki consistency and provenance, use deterministic workflows like ingest, compile, and lint to update memory vault pages, blocks, and source-backed data while preserving page identity and stable navigation.

What is the best way to run a health check on a memory wiki vault?

The best way to run a memory wiki vault health check is to apply a standard maintenance cycle using openclaw wiki lint, which checks accuracy, provenance, and navigability across pages and blocks.

Can I use deterministic workflows to update private memory wiki paths?

Yes, you can update private memory wiki paths using deterministic maintenance workflows that include safe modes, ensuring local and private data remains protected during ingest and compile operations.

Does the memory wiki maintainer preserve Obsidian-friendly links and page identity?

Yes, the memory wiki maintainer preserves page identity and provenance while keeping Obsidian-friendly links intact when applying source-backed updates across the vault.

What do I need to compile and ingest source-backed updates into a memory wiki?

To compile and ingest source-backed updates, you need access to openclaw wiki tooling and guardrails that enforce deterministic workflows and preserve page provenance during vault maintenance.

Why does my memory wiki vault lose navigability after adding new pages?

A memory wiki vault loses navigability when updates bypass deterministic lint and compile workflows, which are required to preserve stable navigation, page identity, and provenance across new blocks.