skills.rest
zhcndoc
zhcndocOFFICIAL
Explore all skills by this author →
WebsiteGitHub

wiki-maintainer

Automate memory wiki vault maintenance with deterministic pages and source-backed updates.

1|Updated Mar 6, 2026
Search Tags:#guidance#provenance#vault-management#openclaw#wiki-maintenance#memory-wiki#deterministic-pages
One-click install
npx skills add https://github.com/zhcndoc/openclaw --skill wiki-maintainer-zhcndoc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-maintainer
Source: https://github.com/zhcndoc/openclaw/tree/main/extensions/memory-wiki/skills/wiki-maintainer
Command: npx skills add https://github.com/zhcndoc/openclaw --skill wiki-maintainer-zhcndoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Memory vaults can drift, be hard to audit, and introduce provenance gaps. Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.

Core Features & Use Cases

  • Deterministic, stable wiki pages with preserved identity across updates.
  • Provenance-first edits using source-backed blocks and citations to external sources.
  • Guided maintenance workflow: wiki_status, memory_search, wiki_search, wiki_get, wiki_apply, wiki_lint, ingest/compile/lint, and bridge/unsafe-local modes.
  • Clear governance for avoiding duplicates, ensuring consistency, and surfacing open questions.

Quick Start

Update a vault page using wiki_apply after inspecting with wiki_get, then run wiki_lint to surface provenance or consistency issues.

Frequently Asked Questions about wiki-maintainer

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

FAQPage Schema
How do I keep memory wiki vault pages accurate and prevent content drift?▼

To maintain a memory wiki vault, inspect pages using wiki_get, apply source-backed updates with wiki_apply, and run wiki_lint to surface provenance or consistency issues. This guided workflow ensures deterministic page identity and prevents content drift across the vault.

What is provenance-first editing for vault management and why is it needed?▼

Provenance-first editing uses source-backed blocks and citations to external sources, ensuring every wiki vault update is traceable and auditable. It is needed to eliminate provenance gaps and avoid duplicate, inconsistent content in memory vaults.

Do I need openclaw wiki tools to run vault maintenance workflows?▼

Yes, openclaw wiki tools are required for vault maintenance. The workflow depends on wiki_status, memory_search, wiki_search, wiki_get, wiki_apply, wiki_lint, wiki_ingest, and wiki_compile, along with bridge and unsafe-local import modes.

How do I surface consistency issues and open questions in a memory wiki?▼

Run wiki_lint after applying updates to surface provenance or consistency issues in the memory wiki. This guided maintenance workflow enforces governance rules to avoid duplicates and highlights open questions across the vault.

What is the best way to update a deterministic wiki page without losing its identity?▼

The best way to update a deterministic wiki page is to inspect it with wiki_get, apply source-backed edits using wiki_apply, and run wiki_lint to verify consistency. This preserves stable page identity across vault updates.

Related Skills

Explore More Content & Communication Skills→
unfinishablemapunfinishablemap
3

apex-evolve

Synthesize multiple sources into Markdown apex articles with frontmatter provenance tracking.

Community
Advanced
karaabd23-cryptokaraabd23-crypto
1

wiki-maintainer

Maintain OpenClaw memory wiki pages with source-backed evidence.

Community
Advanced
borealBytesborealBytes
7

wiki-maintainer

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

Community
Intermediate
majunbaomajunbao

wiki-maintainer

Automate memory wiki vault maintenance with deterministic pages and source-backed updates.

Community
Advanced