wiki-maintainer

Automate deterministic maintenance of a private memory wiki with source-backed updates.

121|17|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Zavianx/velaclaw --skill wiki-maintainer-zavianx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-maintainer
Source: https://github.com/Zavianx/velaclaw/tree/main/extensions/memory-wiki/skills/wiki-maintainer
Command: npx skills add https://github.com/Zavianx/velaclaw --skill wiki-maintainer-zavianx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The memory wiki vault for Velaclaw can become fragmented and opaque without a deterministic workflow and traceable updates.

Core Features & Use Cases

  • Deterministic page generation and updates for memory vaults.
  • Managed blocks to preserve human notes while integrating machine-generated content.
  • Source-backed edits that preserve provenance for each page.

Quick Start

Create a new wiki page for the latest memory artifact and link it to its source reference.

Frequently Asked Questions about wiki-maintainer

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

FAQPage Schema
How do I automate memory wiki updates with source provenance?

Automate memory wiki updates by applying deterministic page generation that preserves source provenance for every edit. This enforces traceable updates across note collections, ensuring each page links back to its original source reference.

What is deterministic page generation for a memory vault?

Deterministic page generation is a structured workflow for memory vault curation that creates and updates wiki pages consistently. It enforces managed blocks to preserve human notes while integrating machine-generated content without fragmentation.

How do I keep human notes intact when adding machine-generated content to a wiki?

Keep human notes intact during wiki updates by using managed blocks that separate human-written content from machine-generated additions. This preserves your original annotations while applying automated, source-backed edits to the memory vault.

What's the best way to maintain a fragmented memory wiki?

The best way to maintain a fragmented memory wiki is applying a deterministic workflow with source-backed edits. This approach enforces managed blocks and preserves provenance, converting opaque note collections into a traceable, up-to-date memory vault.

Can I track provenance for every change made to a memory wiki page?

Yes, you can track provenance for every change by using source-backed edits during page creation and updates. This ensures each modification across the memory vault preserves its source reference, maintaining full traceability.

Does wiki content management work without external dependencies?

Yes, deterministic wiki content management works without external dependencies. It operates directly on note collections to enforce managed blocks and preserve source provenance, requiring no additional components or libraries to maintain your memory vault.