remember

The user wants to save this to long-term memory: $ARGUMENTS

Quick start

memory_save {
  "content": "We rotate JWT refresh tokens on every use; the old token is revoked server-side in auth/refresh.ts.",
  "concepts": "jwt-refresh-rotation, token-revocation, auth-flow",
  "files": "src/auth/refresh.ts"

Expected output:

Why

A memory is only as useful as the terms that retrieve it. Tag with specific concepts so a future recall finds it, and preserve the user's own phrasing.

Workflow

1. Pull the core insight, decision, or fact out of $ARGUMENTS.
2. Extract 2-5 lowercased concept phrases. Prefer specific over generic (jwt-refresh-rotation beats auth).
3. Extract referenced file paths (absolute or repo-relative). Empty if none.
4. Call memory_save with content, concepts (comma-separated string), and files (comma-separated string). In a multi-agent setup pass agentId so the memory lands in the right agent's scope.
5. Confirm the save and echo the concepts so the user knows the retrieval terms.
6. To update a fact, save the corrected version outright: near-duplicate content supersedes the old record, which leaves recall but stays in the version chain.

Anti-patterns

WRONG: concepts: "stuff, code, notes" (generic tags nothing can find later).

RIGHT: concepts: "jwt-refresh-rotation, token-revocation" (specific, retrievable).

Checklist

• Content preserves the user's phrasing, not a paraphrase.
• Concepts are specific, lowercased, 2-5 items.
• File paths are real references, not guesses.
• Confirmation echoes the exact concepts tagged.

See also

• recall: retrieve what you save here (the pair to this skill).
• forget: remove a memory you saved by mistake.
• lesson: behavioral rules from corrections; memories are for facts.
• memory-discipline: when to save unprompted.

Troubleshooting

See ../shared/TROUBLESHOOTING.md if memory_save is not available.