memos-memory
Installation
SKILL.md
MemOS Memory Protocol
Command selection rules:
- if the user asks to uninstall, disable, remove, or stop using MemOS, use
memos uninstall --agent <current_agent> --yesdirectly and do not runmemos searchormemos addfor that turn; add--pathonly when the user also wants to remove the MemOS PATH entries from~/.bash_profileand~/.zshenv; - if the user wants to preview what would be stored, use
memos extractdirectly; - at the start of a conversation, must use
memos searchdirectly with the user's original query; - at the end of a conversation, must use
memos adddirectly with both the user's question and the assistant's final answer; - do not run
memos searchormemos addfor intermediate states, including planning, partial progress, compact/resume, or continuation after context compaction; - if the user wants a memory-aware response from MemOS itself, use
memos chatdirectly; - if the user already has a concrete memory id, use
memos get,memos origin, ormemos deletedirectly; - if the user wants to manage knowledge bases (create, delete, upload, query files), use the corresponding
memos kbsubcommand; - do not call
memos --helpby default when the intent already matches one of the commands below; - use
memos --helponly when the command name, parameters, or route are genuinely unclear; - do not use
memos initas a discovery step when the CLI is already installed.
Identity rules:
- always prefer the exact configured
user_idvalue when a command is scoped by user; - if the user does not specify the
user_id, omit the--user-idargument and use theuser_idfrom the config file by default;