memory-merger

Merge domain memories into instruction files with minimal redundancy.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/afonsoft/VideoChat --skill memory-merger-afonsoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-merger
Source: https://github.com/afonsoft/VideoChat/tree/main/.agents/skills/memory-merger
Command: npx skills add https://github.com/afonsoft/VideoChat --skill memory-merger-afonsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates mature learnings from a domain memory file into its instruction file, preserving knowledge with minimal redundancy.

Core Features & Use Cases

  • Parse Input & Read related files: Identify domain memories and corresponding instruction targets to prepare for merging.
  • Analyze & Propose: Extract relevant memories, propose them for merging, and outline how they fit into instructions.
  • Quality Bar & Iteration: Establish a high-quality merge standard and iteratively refine until alignment is achieved.
  • Update & Cleanup: Apply final merged content to the instruction file and remove processed memories from the source.

Quick Start

Run the memory-merger command with a domain name and optional scope to merge domain memories into the instruction file.

Frequently Asked Questions about memory-merger

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

FAQPage Schema
How do I consolidate domain memory files into instruction prompts?

To consolidate domain memory files into instruction prompts, you run a merge command with a defined memory file and a target instruction file. The process extracts relevant learnings, proposes them for merging, and updates the instruction file while removing processed memories to preserve knowledge with minimal redundancy.

What is the best way to merge mature domain memories into global instruction sets?

Merging mature domain memories into global instruction sets requires defining a target instruction file and specifying scope options like global, user, workspace, or ws. The merge logic analyzes extracted memories, iteratively refines them against a high-quality standard, and applies the final content while preserving context and avoiding duplication.

Can I merge domain memories into workspace-specific instructions without duplicating content?

Yes, you can merge domain memories into workspace-specific instructions without duplicating content by using the workspace or ws scope option. The merge process establishes a high-quality standard, iteratively refines the proposed content to ensure alignment, and applies the final merged content while removing processed memories from the source to prevent redundancy.

Do I need a defined memory file to preserve domain knowledge in instructions?

Yes, you need a defined memory file and a target instruction file to preserve domain knowledge in instructions. The consolidation workflow parses these inputs, extracts relevant mature learnings from the memory file, proposes them for merging into the corresponding instruction target, and cleans up the source memories after applying the final merged content.

Why does merging memories into instruction files require scope options?

Merging memories into instruction files requires scope options to determine the target environment for the preserved knowledge. Specifying global, user, workspace, or ws scopes ensures the merged instruction content is applied to the correct instruction set, maintaining context alignment and preventing redundancy across different operational levels.

How does the memory merger process avoid redundancy when updating instruction files?

The memory merger process avoids redundancy by analyzing and proposing extracted memories before applying them, then iteratively refining the proposed content against a high-quality merge standard. After updating the instruction file with the final merged content, it removes the processed memories from the source file to eliminate duplication.