kb-merge-vault

Merge knowledge base vaults by copying content and resolving conflicts via LLM synthesis.

Updated May 9, 2026
One-click install
npx skills add https://github.com/LuminaVault/LuminaVaultServer --skill kb-merge-vault
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-merge-vault
Source: https://github.com/LuminaVault/LuminaVaultServer/tree/main/hermes-skills/kb-merge-vault
Command: npx skills add https://github.com/LuminaVault/LuminaVaultServer --skill kb-merge-vault

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The KB Merge Vault Skill resolves the issue of merging two knowledge bases (KBs) into a single, coherent source. It automates content copying, conflict resolution, and state reset, streamlining the merging process.

Core Features & Use Cases

  • Vault Merging: Merge a second KB vault into the current one, copying non-conflicting content.
  • Conflict Resolution: Automatically merge conflicting concept articles using LLM synthesis.
  • Manifest and Index Merging: Synthesize manifests and indexes for a full re-synthesis.
  • State Reset: Resets reflect state for a full re-synthesis upon merge completion.
  • Use Case: Ideal for teams combining knowledge bases from different sources or for updating a KB with new information.

Quick Start

Merge a vault by running: /kb-merge-vault <vault-path>

Frequently Asked Questions about kb-merge-vault

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

FAQPage Schema
How do I merge two knowledge base vaults into a single source?

Merging two knowledge base vaults is done by copying non-conflicting content and synthesizing conflicting concept articles using an LLM. This process combines manifests and indexes, resetting reflect state for a full re-synthesis.

How does LLM synthesis resolve conflicts when merging knowledge bases?

LLM synthesis resolves knowledge base merging conflicts by automatically synthesizing conflicting concept articles into a single coherent version. This eliminates manual conflict resolution when updating a KB with new information.

Do I need an LLM to automate vault merging and conflict resolution?

Yes, you need an LLM for conflict resolution and access to the KB vaults to automate vault merging. The LLM synthesizes conflicting concept articles during the merge process.

What happens to manifests and indexes after a knowledge base merge?

Manifests and indexes are merged and synthesized after a knowledge base merge. The process resets reflect state for a full re-synthesis, ensuring the combined vault is coherent.

What is the best way to combine knowledge bases from different sources?

The best way to combine knowledge bases from different sources is automating vault merging to copy non-conflicting content and using LLM synthesis for conflicts. This streamlines updating a KB with new information.

Why does merging knowledge bases require resetting reflect state?

Merging knowledge bases requires resetting reflect state to trigger a full re-synthesis of the combined manifests and indexes. This ensures the newly merged vault maintains a coherent knowledge structure.