/remember
Save an insight, decision, or learning to agentmemory's long-term storage with searchable concept tags. Use when the user says "remember this", "save this", "note that", "don't forget", or wants to preserve knowledge for future sessions.
$ npx -y skills add rohitg00/agentmemory --skill remember --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/remember
Context preview
The summary Claude sees to decide when to auto-load this skill.
Save an insight, decision, or learning to agentmemory's long-term storage with searchable concept tags. Use when the user says "remember this", "save this", "note that", "don't forget", or wants to preserve knowledge for future sessions.
SKILL.md
remember.SKILL.mdname: remember
description: Save an insight, decision, or learning to agentmemory's long-term storage with searchable concept tags. Use when the user says "remember this", "save this", "note that", "don't forget", or wants to preserve knowledge for future sessions.
argument-hint: "[what to remember]"
user-invocable: true
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:
Saved memory abc12345 with 3 concepts: jwt-refresh-rotation, token-revocation, auth-flow.
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). 5. Confirm the save and echo the concepts so the user knows the retrieval terms.
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.
Troubleshooting
See ../_shared/TROUBLESHOOTING.md if `memory_save` is not available.
Read more
name: remember description: Save an insight, decision, or learning to agentmemory's long-term storage with searchable concept tags. Use when the user says "remember this", "save this", "note that", "don't forget", or wants to preserve knowledge for future sessions. argument-hint: "[what to remember]" user-invocable: true
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:
Saved memory abc12345 with 3 concepts: jwt-refresh-rotation, token-revocation, auth-flow.
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). 5. Confirm the save and echo the concepts so the user knows the retrieval terms.
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.
Troubleshooting
See ../_shared/TROUBLESHOOTING.md if `memory_save` is not available.
#1 Persistent memory for AI coding agents based on real-world benchmarks
Repo: rohitg00/agentmemory
Other skills on agentmemory.
- /agentmemory-agents
How agentmemory wires into host coding agents via the connect command. Use when installing agentmemory into a specific agent, when asked which agents are supported, or when a connect adapter writes the wrong config path.
Open skill - /agentmemory-architecture
How agentmemory is built, the iii engine primitives it runs on, its storage model, ports, and the viewer. Use when reasoning about how memory is stored or retrieved end to end, when extending the system, or when answering how agentmemory works under the hood.
Open skill - /agentmemory-config
agentmemory configuration, environment variables, ports, and feature flags. Use when enabling a feature, changing ports, setting an API key, configuring auth, or explaining why a feature is off by default.
Open skill - /agentmemory-hooks
The agentmemory plugin hooks that capture observations automatically across the agent session lifecycle. Use when explaining how memory gets captured without manual saves, when debugging missing observations, or when tuning what gets recorded.
Open skill - /agentmemory-mcp-tools
Map of every agentmemory MCP tool, what each does, and its parameters. Use when choosing which memory tool to call, when a tool name or argument is unclear, or when answering what agentmemory can do via MCP.
Open skill - /agentmemory-rest-api
The agentmemory HTTP REST API surface, the primary protocol for talking to the memory server. Use when calling agentmemory over HTTP, when MCP is unavailable and you need a fallback, or when integrating a host that does not speak MCP.
Open skill

