skills.rest
Jnuso
JnusoCOMMUNITY
Explore all skills by this author →
GitHub

wiki-maintainer

Enforce deterministic pages and source-backed updates in OpenClaw memory wiki vaults.

Updated Apr 8, 2026
Search Tags:#maintenance#memory#provenance#vault#wiki#lint#openclaw
One-click install
npx skills add https://github.com/Jnuso/OpenClaw --skill wiki-maintainer-jnuso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-maintainer
Source: https://github.com/Jnuso/OpenClaw/tree/main/extensions/memory-wiki/skills/wiki-maintainer
Command: npx skills add https://github.com/Jnuso/OpenClaw --skill wiki-maintainer-jnuso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains the OpenClaw memory wiki vault by enforcing deterministic pages, managed blocks, and source-backed updates.

Core Features & Use Cases

  • Prefer wiki_status first when you need to understand the vault mode, path, or Obsidian CLI availability.
  • Prefer memory_search with corpus=all when the shared memory tools are available and you want one recall pass across durable memory plus the compiled wiki.
  • Use wiki_search to discover candidate pages when you want wiki-specific ranking/provenance, then wiki_get to inspect the exact page before editing or citing it.
  • Use wiki_apply for narrow synthesis filing and metadata updates when a tool-level mutation is enough.
  • Run wiki_lint after meaningful wiki updates so contradictions, provenance gaps, and open questions get surfaced before you trust the vault.
  • Use openclaw wiki ingest, openclaw wiki compile, and openclaw wiki lint as the default maintenance loop.
  • In bridge mode, run openclaw wiki bridge import before relying on search results if you need the latest public memory artifacts pulled in.
  • In unsafe-local mode, use openclaw wiki unsafe-local import only when the user explicitly opted into private local path access.
  • Keep generated sections inside managed markers. Do not overwrite human note blocks.
  • Treat raw sources, memory artifacts, and daily notes as evidence. Do not let wiki pages become the only source of truth for new claims.
  • Keep page identity stable. Favor updating existing entities and concepts over spawning duplicates with slightly different names.
  • When creating or refreshing indexes, preserve Obsidian-friendly wikilinks if the vault render mode is obsidian.

Quick Start

Run the wiki maintainer workflow to update the memory wiki with deterministic pages and source-backed edits.

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 memory wiki vault with deterministic pages and source-backed edits?▼

To maintain a memory wiki vault, you enforce deterministic pages, managed blocks, and source-backed updates using linting and managed maintenance loops. This ensures your wiki stays consistent and contradictions are surfaced before you trust the vault.

What is the best way to lint an Obsidian wiki vault for contradictions and provenance gaps?▼

The best way to lint an Obsidian wiki vault is to run a wiki linter after meaningful updates. This surfaces contradictions, provenance gaps, and open questions by validating your managed blocks against the deterministic page rules.

How do I update wiki pages without overwriting human note blocks?▼

To update wiki pages without overwriting human note blocks, keep generated sections inside managed markers. This protects human notes while allowing tool-level mutations and metadata updates for narrow synthesis filing.

Can I use OpenClaw CLI workflows to ingest and compile memory artifacts into a wiki?▼

Yes, you can use OpenClaw CLI workflows to ingest and compile memory artifacts into a wiki. Running ingest, compile, and lint commands forms the default maintenance loop for updating the memory vault.

When should I run bridge import versus unsafe-local import for memory vault maintenance?▼

Run bridge import when you need the latest public memory artifacts pulled in before relying on search results. Use unsafe-local import only when the user explicitly opts into private local path access for memory vault maintenance.

Does wiki maintenance support preserving Obsidian-friendly wikilinks when refreshing indexes?▼

Yes, wiki maintenance supports preserving Obsidian-friendly wikilinks when refreshing indexes. If the vault render mode is Obsidian, creating or refreshing indexes will retain the wikilinks to keep page identity stable.

Related Skills

Explore More Content & Communication Skills→
vignesh2027vignesh2027
18

wiki-maintainer

Automate OpenClaw memory wiki vault maintenance with structured page updates and managed blocks.

Community
Advanced
apexradiusapexradius

distill-memory

Propose durable knowledge candidates for operator-approved inclusion in the knowledge corpus.

Official
Intermediate
borealBytesborealBytes
7

obsidian-vault-maintainer

Maintain Obsidian vaults with wikilinks, frontmatter, and CLI awareness.

Community
Intermediate
mattbeard0mattbeard0

obsidian-markdown

Create and edit Obsidian Markdown notes with wikilinks, embeds, and callouts.

Community
Basic