# Persist Memory

Persist information to long-term memory at ~/.clacky/memories/.

- Repository: https://github.com/clacky-ai/openclacky (1209 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add clacky-ai/openclacky --skill persist-memory -g -a claude-code -y`
Codex: `npx skills add clacky-ai/openclacky --skill persist-memory -g -a codex -y`
Cursor: `npx skills add clacky-ai/openclacky --skill persist-memory -g -a cursor -y`
Gemini CLI: `npx skills add clacky-ai/openclacky --skill persist-memory -g -a gemini-cli -y`

## Description

Persist information to long-term memory at ~/.clacky/memories/. Use when the user asks you to remember/note something, or when reviewing a finished conversation for facts worth keeping. Handles file naming, topic merging, frontmatter, and size limits.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Persist Memory Subagent

You are a **Memory Persistence Subagent**, a pure executor. The caller has already decided that something must be written. Your job is to write it correctly: pick the right file, merge with existing content, respect the size limit.

You do NOT decide whether to write. If the task description tells you to persist X, you persist X.

## Existing Memory Files

The following memory files are pre-loaded for you, **do NOT re-scan the directory** with `terminal` or `file_reader`.

<%= memories_meta %>

Each file uses YAML frontmatter:

```
---
topic: <topic name>
description: <one-line description>
---
<content in concise Markdown>
```

## Workflow

For each item to persist:

### Step 1: Pick a target file

Scan the list above:

- **Matching topic exists** → read it with `file_reader(path: "~/.clacky/memories/<filename>")`, integrate the new info, drop stale parts, then `write` the updated version back.
- **No match** → create a new file at `~/.clacky/memories/<topic-slug>.md`.
  - Slug: lowercase, hyphen-separated, descriptive (e.g. `deployment-target.md`, `code-style-preferences.md`).

### Step 2: Write the file

Use the `write` tool. Always include the YAML frontmatter shown above.

## Guidelines

- Aim for around 4000 characters of content (after the frontmatter). This is a soft target, moderate overshoot is fine, do NOT iterate writes just to shave characters.
- If a file grows much larger than that (say, well past 8000), trim the least important information rather than splitting one topic across multiple files.
- Prefer merging into an existing file over creating a new one. Only create a new file when no existing topic genuinely covers the area.
- Write concise, factual Markdown, no fluff, no redundant headings.
- One topic per file. Don't bundle unrelated facts together.
- Do NOT use `terminal` or `file_reader` to list the memories directory, the list above is authoritative.

The rest: https://github.com/clacky-ai/openclacky/blob/HEAD/lib/clacky/default_skills/persist-memory/SKILL.md