memory-organizer

Compress agent conversations into traceable records across memory files.

1.2k|101|Updated May 25, 2025
One-click install
npx skills add https://github.com/ZHangZHengEric/Sage --skill memory-organizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-organizer
Source: https://github.com/ZHangZHengEric/Sage/tree/main/app/skills/memory-organizer
Command: npx skills add https://github.com/ZHangZHengEric/Sage --skill memory-organizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) components.

What problem does it solve?

The Memory Organizer helps teams and agents automatically extract, categorize, and consolidate reusable information from dense conversations into a structured memory repository, enabling faster retrieval and knowledge sharing. It ensures that only non-sensitive, prep-for-use insights are moved to long-term memory when explicitly triggered by the user.

Core Features & Use Cases

  • Intelligent conversation analysis: compress and summarize dialogues into concise, traceable records spanning USER.md, AGENT.md, MEMORY.md, memory/, IDENTITY.md, and SOUL.md.
  • Memory governance: maintain a memory index (MEMORY.md) and a detailed history under memory/ for auditability and traceability.
  • Safety-first workflow: explicit user-triggered memory actions ensure privacy and minimize unintended data writes.
  • Customizable templates: adapt writing rules and evidence linking to fit project-specific memory schemas.

Quick Start

对指定 Agent 的对话进行压缩,并在需要时生成记忆落地的输出。

Frequently Asked Questions about memory-organizer

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

FAQPage Schema
How do I compress and summarize agent conversations into a knowledge base?

You can compress and summarize agent conversations into a knowledge base by triggering this Skill to filter essential messages via API and write traceable records into structured markdown files like MEMORY.md and SOUL.md.

How does conversation compression handle privacy sensitivities before writing to disk?

Conversation compression handles privacy sensitivities by validating data before any write operations, ensuring only non-sensitive insights are moved to long-term memory storage when explicitly triggered by the user.

Can I automatically route extracted conversation data into specific markdown files?

You can route extracted conversation data into specific markdown files by indexing summarized information across USER.md, AGENT.md, MEMORY.md, memory/, IDENTITY.md, and SOUL.md for structured long-term knowledge management.

Does the memory organizer require explicit user triggers to write conversation history?

Yes, the memory organizer requires explicit user triggers to write conversation history, enforcing a safety-first workflow that minimizes unintended data writes and maintains auditability through a detailed memory index under memory/.

What is the best way to maintain a memory index for long-term agent knowledge management?

Maintaining a memory index for long-term agent knowledge management involves consolidating reusable information into MEMORY.md while storing detailed traceable history under the memory/ directory for auditability.