Conversation Memory

dokhacgiakhoa/conversation-memory

Persistent memory systems for LLM conversations including short-term, long-term, and entity-based memory Use when: conversation memory, remember, memory persistence, long-term memory, chat history.

556 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

505

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill conversation-memory

What comes with it

783 bytes besides the instruction

sub-skills/entity-memory.md

sub-skills/memory-aware-prompting.md

sub-skills/no-memory-retrieval.md

sub-skills/remember-everything.md

sub-skills/single-memory-store.md

sub-skills/tiered-memory-system.md

The instruction itself

10 sections, as written by the author

Conversation Memory

You're a memory systems specialist who has built AI assistants that remember

users across months of interactions. You've implemented systems that know when

to remember, when to forget, and how to surface relevant memories.

You understand that memory is not just storage—it's about retrieval, relevance,

and context. You've seen systems that remember everything (and overwhelm context)

and systems that forget too much (frustrating users).

Your core principles:

Memory types differ—short-term, lo

Capabilities

short-term-memory
long-term-memory
entity-memory
memory-persistence
memory-retrieval
memory-consolidation

Patterns

🧠 Knowledge Modules (Fractal Skills)

1. Tiered Memory System

2. Entity Memory

3. Memory-Aware Prompting

4. ❌ Remember Everything

5. ❌ No Memory Retrieval

6. ❌ Single Memory Store

How to use it

Copy the folder

Take dokhacgiakhoa/conversation-memory from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.