mem0-remember

Stores user-provided facts into mem0 memory with type classification and metadata.

1|Updated Jan 13, 2022
One-click install
npx skills add https://github.com/jayho-k/TIL --skill mem0-remember-jayho-k
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mem0-remember
Source: https://github.com/jayho-k/TIL/tree/main/AI/mem0/code/mem0_code_analize/mem0/integrations/mem0-plugin/.opencode-plugin/opencode-skills/mem0-remember
Command: npx skills add https://github.com/jayho-k/TIL --skill mem0-remember-jayho-k

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers often want to persist decisions, preferences, conventions, and learnings during a coding session, but manually recording them breaks flow. This Skill captures a verbatim fact from user input and stores it in mem0 with proper classification and metadata so it can be retrieved later. ## Core Features & Use Cases - Explicit Memory Storage: Stores user-provided text verbatim via the mem0 add_memory API with infer disabled, since the user stated the fact directly. - Automatic Type Classification: Classifies content into decision, anti_pattern, user_preference, convention, task_learning, or environmental based on content signals. - Async Write Confirmation: Polls get_event_status with the returned event_id to confirm the write succeeded and report the memory ID. - Use Case: While working in OpenCode, you realize your team always uses pnpm instead of npm. Say "remember this: we always use pnpm for package management" and the fact is stored as a convention tied to your user, project, and branch. ## Quick Start Ask the assistant to remember a specific fact, decision, or preference, for example by saying remember this: we decided to deploy on Fridays only.

Frequently Asked Questions about mem0-remember

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save a memory in mem0 from a coding assistant?

Provide the fact as text to the remember command, and the skill calls add_memory with your user ID, project ID, and metadata. The write is asynchronous, so the event status is checked once to confirm storage and return the memory ID.

What memory types does mem0 support for classification?

This skill classifies memories into decision, anti_pattern, user_preference, convention, task_learning, and environmental types. Classification is based on content signals such as "we decided" for decisions or "I prefer" for user preferences.

Why does add_memory return an event_id instead of a memory_id?

Mem0 writes are asynchronous, so add_memory returns an event_id representing the queued write operation. You must call get_event_status with that event_id to confirm completion and retrieve the actual memory ID once the status is SUCCEEDED.

When should I use infer=False when adding memories to mem0?

Use infer=False when the user explicitly states a fact and no extraction or inference is needed. This stores the text verbatim with confidence 1.0, avoiding any reinterpretation of the user's exact wording.

What happens if the mem0 write is still pending?

If get_event_status returns PENDING or processing, the skill reports the memory as stored using the event ID as a fallback reference. The write will complete asynchronously in the background.