memory

Load MEMORY.md into context and search HISTORY.md with grep-style tools.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/DaTingLi/heimaclaw --skill memory-datingli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/DaTingLi/heimaclaw/tree/main/reference/nanobot/nanobot/skills/memory
Command: npx skills add https://github.com/DaTingLi/heimaclaw --skill memory-datingli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Two-layer memory helps AI agents retain important facts and project context across sessions, while separating transient conversations from persistent knowledge.

Core Features & Use Cases

  • Long-term memory loaded into context from MEMORY.md.
  • Append-only event history in HISTORY.md, searchable with grep-style tools.
  • Use Case: maintain continuity across chats, remember decisions, and reference past knowledge to improve responses.

Quick Start

Load MEMORY.md into the AI context and enable grep-based search over HISTORY.md.

Frequently Asked Questions about memory

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

FAQPage Schema
How do I maintain persistent context and recall past decisions across AI agent sessions?

Long-term memory is preserved by loading MEMORY.md into the AI context and offering grep-style search over HISTORY.md. This two-layer approach separates permanent facts from append-only event logs, maintaining continuity across chats.

What is the best way to search historical events in an AI agent memory system?

The best way to search historical events is using grep-style search tools over the HISTORY.md file. This append-only event log captures past decisions and actions, allowing agents to reliably reference specific past knowledge.

How does two-layer memory management work for AI agents?

Two-layer memory management works by separating persistent knowledge from transient history. MEMORY.md provides long-term context loaded directly into the agent, while HISTORY.md functions as an append-only log for searchable event recall.

Do I need to load MEMORY.md manually to enable persistent context in my AI workflows?

Yes, the design requires loading MEMORY.md into the AI context to enable persistent context. This ensures important facts and project knowledge are available immediately, while HISTORY.md handles the event search logs.

When do I need to separate transient conversations from persistent knowledge in AI chats?

Separation is needed when an AI agent must retain important facts and project context across sessions. Using MEMORY.md for permanent knowledge and HISTORY.md for append-only logs prevents transient chat data from overwriting critical decisions.