wiki-maintainer

Maintain OpenClaw memory wiki pages with source-backed evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures the OpenClaw memory wiki stays up-to-date with deterministic pages and traceable provenance.

Core Features & Use Cases

  • Deterministic page updates using standardized blocks and sources.
  • Guided workflow with wiki_status, memory_search, wiki_search, wiki_get, wiki_apply, and wiki_lint for auditing, retrieval, and mutation.
  • Reconcile memory artifacts with wiki entries and preserve page identity and provenance.

Quick Start

Run the wiki-maintainer workflow to audit and update memory wiki pages with source-backed evidence.

Frequently Asked Questions about wiki-maintainer

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

FAQPage Schema
How do I keep a memory wiki up-to-date with source-backed evidence?

Reconciling memory artifacts with wiki entries involves auditing vault content using wiki_status and memory_search, then applying standardized page updates with wiki_apply to ensure entries match the underlying memory artifacts.

Can I audit vault content and preserve page identity when indexing new notes?

Yes, you can audit vault content and safely index new notes using the wiki_lint tool, which ensures deterministic page updates while strictly preserving existing page identity and provenance.

What is the best way to reconcile memory artifacts with wiki entries?

Reconciling memory artifacts with wiki entries involves auditing vault content using wiki_status and memory_search, then applying standardized page updates with wiki_apply to ensure entries match the underlying memory artifacts.

Do I need in-memory tools like wiki_search and wiki_get to maintain my memory wiki?

Yes, maintaining the memory wiki requires in-memory tools such as wiki_search, wiki_get, and wiki_status to retrieve existing pages and source-backed evidence before applying any deterministic updates.

Why does wiki maintenance require deterministic pages and traceable provenance?

Wiki maintenance requires deterministic pages and traceable provenance to ensure that every update is source-backed, preventing unverified information from overwriting established memory artifacts.