save-memory

Files (1)

• SKILL.md

SKILL.md (first lines)

# Save Memory Skill

When the user asks to remember something:

1. First read the current `memory.md`
2. Then call `write_file` with path `memory.md` and the COMPLETE updated content
3. Tell the user the change is waiting for their approval. `write_file` on
   `memory.md` only *proposes* the change: the user sees the diff in the
   conversation and accepts or rejects it. Never say it was saved.

**CRITICAL:** Only use the file `memory.md`. Never create other files like `notes/`, `preferences.md`, etc. All memories go in `memory.md`.

Step 1 is not optional. `memory.md` is hand-curated and has no history in the
vault, so a write that would sharply shrink it is refused unless this turn has
actually read the file it is replacing. Never reconstruct it from memory of an
earlier turn, and never write a summary of it — write the full text with your
change applied. The previous version is kept in a rolling backup set, but that
is a safety net, not a substitute for reading first.

From borismus/alloy, MIT.

More from borismus/alloy