---
name: coppermind-memory-saver
description: "Use Coppermind MCP to capture durable preferences, decisions, and project facts."
---

# Coppermind Memory Saver

Use this skill when a conversation contains durable information that Coppermind should remember for later. The goal is to save stable facts, not to archive every message.

## Save by default when the information is durable

Save the information when it is any of the following:

- a stable user preference
- a recurring workflow or constraint
- a project decision
- a durable environment fact
- a long-lived goal or plan
- a user-requested memory

Examples:

- "I prefer concise answers."
- "The default runtime is local-first."
- "This project uses Codex and MCP."
- "The user is working from a Mac today."

## Do not save transient or sensitive information

Do not save:

- passwords, secrets, tokens, API keys, or session cookies
- one-off debugging noise
- short-lived plans or scratch notes
- ephemeral conversation fluff
- private information unless the user clearly asked to store it

If a fact looks sensitive or ambiguous, ask before saving.

## When to ask for confirmation

Ask first when:

- the memory may be personal or sensitive
- it is unclear whether the fact is durable
- the user seems to be brainstorming rather than deciding
- the memory would be surprising if recalled later

## How to write a memory

When saving, write one concise fact per memory:

- use the shortest durable phrasing
- prefer first-person wording for user preferences
- include just enough context to make the memory useful later
- add a simple tag for the category when it helps retrieval

## Recommended Coppermind actions

- use `memory_ingest` to save the durable fact
- use `memory_search` to verify what is already stored
- use `memory_get` when you need the broader recall view
- use `memory_delete` when the user asks to forget something

## Practical rule

If a fact would still matter tomorrow, next week, or next month, it probably belongs in Coppermind.