メニュー
Stores a memory verbatim from user input with appropriate type classification and metadata. Use when the user says remember this, save this, store this, note that, or explicitly asks to record a decision, preference, convention, or learning.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Searches and injects relevant memories into context before starting work on a task. Use when beginning a new task, switching context, or when project history, past decisions, or coding conventions need to be loaded.
Consolidates stored memories by merging duplicates, resolving contradictions, and pruning stale entries. Use when memory count is high, search results feel noisy or repetitive, or periodic cleanup is needed to maintain memory quality.
Deletes memories by search query or memory ID with confirmation before removal. Use when removing outdated decisions, incorrect memories, sensitive data, or cleaning up after experiments. Also handles undo of recent additions.
Pins or unpins a memory to protect it from pruning during dream consolidation. Use when a memory is critical and must never be removed, such as architecture decisions, security constraints, or immutable team conventions.
Stores a memory verbatim from user input with appropriate type classification and metadata. Use when the user says remember this, save this, store this, note that, or explicitly asks to record a decision, preference, convention, or learning.
Views or changes the default memory scope (project, session, or global) used when saving and searching memories. Use when the user wants to control whether memories are scoped to this repo, this run, or shared across all their projects.
| name | remember |
| description | Stores a memory verbatim from user input with appropriate type classification and metadata. Use when the user says remember this, save this, store this, note that, or explicitly asks to record a decision, preference, convention, or learning. |
Store a fact or learning directly into mem0.
The user provides the content as an argument: /mem0:remember <text>
If no text was provided, ask: "What should I remember?"
Based on the content, pick the best metadata.type:
| Content signal | Type |
|---|---|
| "we decided...", "always use...", "never..." | decision |
| "X doesn't work because...", "don't try..." | anti_pattern |
| "I prefer...", "use X instead of Y" | user_preference |
| "the convention is...", "we always..." | convention |
| "learned that...", "figured out..." | task_learning |
| setup, env, tooling, config | environmental |
| anything else | task_learning |
Call add_memory with:
text="<the user's text>"user_id=<active_user_id>app_id=<active_project_id>metadata={"type": "<classified_type>", "branch": "<active_branch>", "confidence": 1.0, "source": "remember_command"}infer=Falseinfer=False because the user stated the fact explicitly — no extraction needed.
confidence=1.0 because the user explicitly asked to store this.
The add_memory response returns event_id (not memory_id) because writes are async.
Call get_event_status(event_id=<event_id>) once.
SUCCEEDED: print the memory ID from the result.PENDING or processing: print with the event ID as fallback.Remembered as <type>: "<content, first 80 chars>"
Memory ID: <id from event status>
Append ... only if content was truncated (longer than 80 chars).