wiki-maintainer

Maintain Obsidian wiki vaults with deterministic page updates and source-backed synchronization.

2|Updated May 23, 2026

Search Tags:#linting #knowledge management #provenance #obsidian #wiki #source-backed #vault maintenance

Ready to run

npx skills add https://github.com/enclawed/enclawed-oss --skill wiki-maintainer-enclawed

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wiki-maintainer
Source: https://github.com/enclawed/enclawed-oss/tree/main/extensions/memory-wiki/skills/wiki-maintainer
Command: npx skills add https://github.com/enclawed/enclawed-oss --skill wiki-maintainer-enclawed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps a memory wiki vault organized, consistent, and grounded in real sources so updates do not drift into duplicate pages or unsupported claims.

Core Features & Use Cases

Deterministic maintenance: Use the vault status, search, apply, ingest, compile, and lint flow to keep pages current and reliable.
Provenance-aware editing: Preserve source-backed evidence, stable page identity, and managed blocks while updating wiki content.
Operational use cases: Maintain a team knowledge vault, refresh indexed pages after new evidence arrives, and surface contradictions or open questions before trusting the vault.

Quick Start

Use this skill to ingest the latest sources, compile the vault, and run a lint pass after making wiki updates.

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 wiki vault and prevent duplicate pages after new updates?▼

Vault maintenance prevents duplicate pages and unsupported claims by applying deterministic page updates with stable identity, managed blocks, and source-backed synchronization. It uses status checks, search, apply, ingest, compile, and lint workflows to keep content current.

How does source-backed synchronization work for knowledge management in Obsidian?▼

Source-backed synchronization works by preserving provenance evidence and stable page identity during updates. It enforces managed marker boundaries around content blocks, ensuring wiki edits remain grounded in real sources and do not drift into unsupported claims.

What's the best way to lint a wiki for contradictions and open questions?▼

The best way to lint a wiki for contradictions is running a post-edit lint pass after compiling and applying updates. This linting process surfaces conflicting claims and open questions before you trust the vault, ensuring knowledge consistency.

Can I ingest external sources into my knowledge vault using a CLI-driven environment?▼

Yes, you can ingest external sources into your knowledge vault using CLI-driven environments or Obsidian-based workflows. The ingest workflow imports new evidence, compiles indexed pages, and synchronizes content while preserving source provenance.

Why does my wiki vault need provenance preservation during page updates?▼

Your wiki vault needs provenance preservation to ensure every claim remains grounded in real sources. Without preserving source-backed evidence during managed block updates, wiki content drifts into unsupported claims, duplicate pages, and untraceable contradictions.

Does wiki vault maintenance work without external dependencies?▼

Yes, wiki vault maintenance works without external dependencies. It operates within Obsidian-based or CLI-driven environments using internal workflows for status checks, search, apply, ingest, compile, lint, and bridge imports to manage page consistency.