wiki-maintainer

Ingest, compile, and lint OpenClaw memory wiki vault pages.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/wangqianCAI/OBI --skill wiki-maintainer-wangqiancai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-maintainer
Source: https://github.com/wangqianCAI/OBI/tree/main/extensions/memory-wiki/skills/wiki-maintainer
Command: npx skills add https://github.com/wangqianCAI/OBI --skill wiki-maintainer-wangqiancai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of maintaining a fragmented knowledge base by providing a structured, deterministic workflow for managing wiki pages, ensuring consistency between raw memory artifacts and compiled documentation.

Core Features & Use Cases

  • Automated Maintenance: Orchestrates the ingest, compile, and lint loop to keep wiki pages accurate and up-to-date.
  • Provenance Tracking: Ensures that wiki content remains linked to raw sources and daily notes, preventing the creation of isolated or duplicate information.
  • Use Case: When you have accumulated a large volume of daily notes and memory artifacts, use this skill to compile them into a structured, searchable wiki vault while automatically identifying contradictions or missing provenance.

Quick Start

Use the wiki-maintainer skill to ingest new memory artifacts and lint the current vault for consistency.

Frequently Asked Questions about wiki-maintainer

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

FAQPage Schema
How do I synchronize raw memory artifacts with compiled documentation pages?

To synchronize memory artifacts with compiled documentation pages, run an automated ingestion, compile, and lint loop within local or bridge-mode environments to maintain wiki vault integrity and ensure reliable knowledge retrieval.

What is the best way to maintain consistency across a fragmented knowledge base?

Maintaining consistency across a fragmented knowledge base requires a deterministic workflow that orchestrates linting and compilation, preventing isolated or duplicate information by linking wiki content directly to raw sources and daily notes.

How does provenance tracking work for daily notes in a memory wiki?

Provenance tracking for a memory wiki works by ensuring compiled wiki pages remain consistently linked to raw memory artifacts and daily notes, which prevents the creation of isolated information and enables accurate source verification.

Can I use local or bridge-mode environments to compile daily notes into a searchable wiki?

Yes, you can operate within local or bridge-mode environments to compile accumulated daily notes and memory artifacts into a structured, searchable wiki vault while automatically identifying contradictions or missing provenance.

Why does my wiki vault need managed markers and stable page identity?

Your wiki vault needs managed markers and stable page identity to ensure reliable knowledge retrieval and provenance tracking during the automated ingestion and linting processes, maintaining structural integrity across synchronization.