wiki-maintainer

Lint Brikko Studio wiki vaults for provenance gaps and contradictions.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/brikkoAI/brikko-studio --skill wiki-maintainer-brikkoai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-maintainer
Source: https://github.com/brikkoAI/brikko-studio/tree/main/packages/core/extensions/memory-wiki/skills/wiki-maintainer
Command: npx skills add https://github.com/brikkoAI/brikko-studio --skill wiki-maintainer-brikkoai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent, unsubstantiated, or contradictory content in Brikko Studio memory wiki vaults, ensuring all stored knowledge is accurate, traceable to original sources, and aligned with durable shared memory artifacts and raw source data.

Core Features & Use Cases

  • Deterministic Page Management: Maintains stable wiki page identities and preserves human-authored note blocks inside managed markers to avoid overwriting user-generated content during updates.
  • Source-Backed Content Rules: Requires all new claims in wiki pages to be backed by raw memory artifacts, daily notes, or other evidence sources, preventing the wiki from becoming the sole source of truth for new information.
  • Automated Vault Linting: Runs built-in linting after meaningful updates to surface contradictions, provenance gaps, and open questions before the vault is trusted for decision-making or AI context use.
  • Use Case: For teams using Brikko Studio's memory wiki to store shared institutional knowledge, this Skill ensures all content remains reliable, traceable, and free of duplicate or conflicting entries across all supported vault modes including bridge and unsafe-local.

Quick Start

Use the wiki-maintainer skill to run a full lint pass on your active memory wiki vault and resolve any surfaced provenance gaps or contradictions.

Frequently Asked Questions about wiki-maintainer

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

FAQPage Schema
How do I validate provenance for claims in a memory wiki vault?

To validate provenance in a memory wiki vault, all new claims must be backed by raw memory artifacts or evidence sources. Source-backed content rules prevent the wiki from becoming the sole source of truth, ensuring traceability.

How do I preserve human-authored note blocks during automated wiki page updates?

To preserve human-authored note blocks during wiki page updates, managed markers are used to protect user-generated content. This deterministic page management maintains stable wiki page identities without overwriting existing notes.

What is vault linting and when do I need it for shared memory artifacts?

Vault linting is the process of scanning memory wiki vaults to surface contradictions, provenance gaps, and open questions. You need it after meaningful updates to ensure the vault is trusted for decision-making or AI context use.

Can I use Obsidian-compatible wiki rendering with bridge and unsafe-local import modes?

Yes, Obsidian-compatible wiki rendering is supported alongside bridge and unsafe-local import modes for public and private memory sources. This ensures consistent content management across all supported vault configurations.

Why does my wiki vault contain contradictory entries and unsubstantiated claims?

Contradictory entries and unsubstantiated claims occur when wiki content is not validated against raw source data. Without automated linting and provenance validation, unverified information accumulates in shared institutional knowledge.

Does wiki maintenance work for teams using durable shared memory in Brikko Studio?

Yes, wiki maintenance works for teams using Brikko Studio's memory wiki to store shared institutional knowledge. It ensures all content remains reliable, traceable, and free of duplicate or conflicting entries across supported vault modes.