← ClaudeAtlas

engramorylisted

Curated, file-based long-term memory for an AI agent. Use this skill (1) at the start of a task or when resuming unfinished work to recall via the memory index, (2) during a task to save durable user, feedback, project, or reference facts, (3) when a task finishes, to run the completion checkpoint — promote what is durable, retire what was only transient, and write nothing when nothing qualifies (an empty checkpoint still has to be decided) — and (4) before compacting, clearing context, or opening a fresh thread to sync the current goal, state, decisions, constraints, blockers, and next step. Each memory is one small markdown file; a single always-loaded index (MEMORY.md) lists them. Works on any agent host that can read and write local files.
tinqiao-oss/engramory · ★ 204 · AI & Automation · score 87
Install: claude install-skill tinqiao-oss/engramory
# Engramory — curated file-based long-term memory Engramory is a *discipline*, not a database. Memory is a directory of small, human-readable markdown files plus one index. There is no vector store, no embeddings, no server. You (the agent) read the index, open the files that matter, and keep the store clean over time. This file is self-contained: it defines the full storage layout, the recall protocol, the write protocol, and the curation rules. A host that loads this file as standing instructions and can read/write files can use Engramory even if it has no built-in memory feature. --- ## 0. Where memory lives Memory lives under a single root directory, `<MEMORY_ROOT>`, that the **user can see, open, and audit**. Human-readability is the whole point — never hide the store somewhere the user will not look. This directory is the **one canonical Engramory store** for both durable memory and resumable project state. Do not create a second "handoff" memory type or a parallel handoff store: unfinished-task continuity belongs in a `project` note and follows the same index, dedup, correction, and retirement rules. - Default: a `memory/` directory the user configures (e.g. inside their notes folder, or a `memory/` folder at the root of the active project). - It MUST be configurable; never hard-code an absolute path in the skill. - If `<MEMORY_ROOT>` lives inside a git repository, it MUST be git-ignored — memories routinely contain machine-local, sensitive but non-credentia