memory-triage

Extract and store durable facts from conversations into mem0 long-term memory.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI agents lose all context between sessions, forcing users to repeat preferences, configurations, and decisions. This Skill evaluates each conversation turn and persists only durable, actionable facts to mem0 long-term memory so future sessions start with relevant context. ## Core Features & Use Cases - Four-Gate Fact Triage: Every candidate fact must pass future-utility, novelty, factual, and safety gates before storage, preventing memory pollution from small talk, tool output, and transient state. - Categorized Memory Operations: Store, search, update, consolidate, and delete memories across eight categories (identity, preference, decision, rule, project, configuration, technical, relationship) with per-category retention policies. - Credential Safety: Never stores secrets or tokens; records only that a credential was configured, with pattern-based detection of API keys and auth tokens. - Use Case: A user mentions they switched monitoring from Datadog to Grafana due to cost. The Skill stores a temporally anchored decision memory, and weeks later a new agent session recalls this context when the user asks about their observability stack. ## Quick Start Ask the agent to remember that you prefer terse responses with no trailing summaries, and it will store that preference for all 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 with mem0?

Use the memory_add tool with a facts array and a category such as identity, preference, or decision. Facts must be self-contained third-person statements of 15-50 words, grouped by entity, and all facts in one call must share the same category.

What types of information should be stored in agent long-term memory?

Store identity details, standing rules, configurations, preferences with rationale, project milestones, technical stack, relationships, and decisions. Skip tool outputs, one-time commands, acknowledgments, transient states, and anything already recalled without material change.

Does mem0 memory storage handle API keys and credentials safely?

Yes. The safety gate scans for credential prefixes, tokens, webhook URLs, and key-value assignment patterns. Matching values are never stored; instead the memory records only that a credential was configured, with a date anchor.

How do I update an existing memory instead of creating duplicates?

Call memory_search to locate the existing memory, then memory_update with the memory ID and revised text. Update is atomic and preserves edit history, and is preferred over delete-plus-add when facts materially change.

Why does memory_search return poor results for conversational queries?

Raw user messages contain noise words that dilute vector similarity. Rewrite queries as 3-6 keyword index terms using third-person storage language like 'user', 'decided', or 'prefers', dropping question words and pronouns.

What environment variables does the openclaw mem0 memory skill require?

The skill metadata requires MEM0_API_KEY, OPENAI_API_KEY, and ANTHROPIC_API_KEY environment variables. It is loaded by the openclaw-mem0 plugin when skills mode is active and is not user-invocable directly.