memory-triage

Extracts and stores durable user facts from conversations into mem0 long-term memory.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/nhatnguyen1122/Agent-Memory-Eval --skill memory-triage-nhatnguyen1122
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-triage
Source: https://github.com/nhatnguyen1122/Agent-Memory-Eval/tree/main/mem0/integrations/openclaw/skills/memory-triage
Command: npx skills add https://github.com/nhatnguyen1122/Agent-Memory-Eval --skill memory-triage-nhatnguyen1122

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Conversational agents forget everything between sessions, forcing users to repeat their identity, preferences, rules, and project context. This Skill evaluates each conversation turn and persists only the facts worth remembering into mem0 long-term memory. ## Core Features & Use Cases - Four-Gate Triage: Every candidate fact must pass future-utility, novelty, factual, and safety gates before storage, so most turns correctly produce zero memory operations. - Categorized Storage: Facts are stored via memory_add under categories (identity, preference, decision, rule, project, configuration, technical, relationship) that control retention policy. - Recall Protocol: A companion protocol defines how to rewrite user messages into 3-6 keyword search queries and apply time/category filters for memory_search. - Credential Safety: Secrets and tokens are never stored; only the fact that a credential was configured is recorded. - Use Case: A user says "I'm Sarah, I work at Cloudflare, and we just switched monitoring from Datadog to Grafana because of cost." The Skill stores one identity fact and one decision fact in separate categorized calls, then recalls them in future sessions. ## Quick Start Ask the agent to remember that you prefer terse responses with no trailing summaries, and it will store that preference in long-term memory for future sessions.

Frequently Asked Questions about memory-triage

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

FAQPage Schema
How do I add long-term memory to an AI agent?

Use memory_add with a facts array and a category such as identity, preference, decision, or rule. Each fact must pass four gates: future utility, novelty, factual concreteness, and credential safety. Facts in different categories require separate calls.

How do I search stored memories effectively?

Rewrite the user's message into a 3-6 keyword query using entity names and storage language like "user prefers" or "decided", dropping question words and pronouns. Add created_at or category filters only when the user signals time or category constraints.

What information should never be stored in agent memory?

Never store credentials, tokens, raw tool output, one-time commands, acknowledgments, transient status, or generic small talk. For credentials, record only that the credential was configured with a date, never the value itself.

How do I update an existing memory instead of duplicating it?

Run memory_search to find the existing memory ID, then call memory_update with the combined, more complete text. Update only when the new information adds real context; cosmetic rephrasing should be skipped.

Does memory-triage work without API keys configured?

No. The Skill requires MEM0_API_KEY, OPENAI_API_KEY, and ANTHROPIC_API_KEY environment variables, as declared in its openclaw plugin metadata. It is loaded by the openclaw-mem0 plugin when skills mode is active.