memory

Store and retrieve long-term knowledge across sessions using managed memory files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/timothyckl/nano-hermes --skill memory-timothyckl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/timothyckl/nano-hermes/tree/main/nano_hermes/skills/memory
Command: npx skills add https://github.com/timothyckl/nano-hermes --skill memory-timothyckl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a persistent, two-layer memory system to maintain long-term facts and recent context for an AI agent, reducing the need to repeatedly load data and enabling continuity across sessions.

Core Features & Use Cases

  • Dream-managed memory components: SOUL.md, USER.md, and MEMORY.md are automatically maintained to preserve personality, user preferences, and project knowledge.
  • memory/history.jsonl serves as an append-only log of historical events for auditing, while only curated context is loaded into active sessions.
  • Use cases include maintaining user profiles, project context, and long-running subagents across multiple interactions.

Quick Start

Enable the memory system for the current session and begin tracking user preferences and project history.

Frequently Asked Questions about memory

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

FAQPage Schema
How do I maintain AI agent context and persistent memory across multiple sessions?

To maintain AI agent context across sessions, use a two-layer memory architecture that stores long-term knowledge in managed markdown files and logs historical events in an append-only history file for persistent user profiles and project context.

What is a two-layer memory architecture for persistent AI assistants?

A two-layer memory architecture separates curated context from raw history by managing active knowledge in markdown files and logging events in an append-only history file. This approach supports persistent user profiles and historical auditing without reloading data.

Can I use an append-only history log to audit long-running AI agent memory?

Yes, you can use an append-only history log to audit long-running AI agent memory. The system records historical events to a history file while loading only curated context into active sessions, ensuring persistence and auditability across interactions.

Does the memory system support updating user profiles and project knowledge automatically?

Yes, the memory system supports updating user profiles and project knowledge automatically. It uses managed markdown files to preserve personality, user preferences, and ongoing project context, enabling continuous memory updates across multiple interactions.

What is the best way to store long-term facts for project-oriented AI agents?

The best way to store long-term facts for project-oriented AI agents is a persistent memory architecture using managed knowledge files. This maintains ongoing project context and historical events, reducing the need to repeatedly load data across sessions.

When do I need persistent memory for a personal assistant AI agent?

You need persistent memory for a personal assistant AI agent when it must maintain long-term facts, user preferences, and historical context across multiple sessions. This prevents repeated data loading and ensures continuity in ongoing interactions.