Use the memmy-memory CLI when an agent needs to check the Memory service, open or close agent sessions, start or complete turns, search, add, read, or delete memories, or call uncommon HTTP routes through raw requests.
SkillScore79Maintained
Automatic
◆AI Engineer pack
Last verified 8/19/2026
What it changes
Passed 16 of 20 test cases with the skill, and 8 of 20 without it.
Without skill38%
With skill79%
Checks it passed that the model alone missed
Includes `--source codex` flag.
Uses `memmy-memory turn start`.
Includes `--source cursor` flag.
and 9 more in the full report
10 fixed9 passed either way5 still failing0 broke
Pass-rate lift
+42 pp
Tokens
+2%
Agent turns
0%
Response time
-52%
Model gemini-3.6-flashMeasured 8/19/2026v119 of 24 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
The user explicitly asked us to remove memory record `mem-30192` because it contains obsolete staging server URLs. What command should be executed to remove it?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses `memmy-memory delete` with record ID `mem-30192`.
Missed
Passed
case-11 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md44 lines11 files
Memmy Memory CLI
Use this skill when the task needs persistent agent memory through the memmy-memory command.
Command Selection
Check availability: read health.
Create or resume a session: read session open.
Close a session: read session close.
Begin a turn and retrieve prompt context: read turn start.
Finish a turn and write memory: read turn complete.
Search memory: read search.
Add a memory manually: read add.
Read one memory by id: read get.
Delete one memory by id: read delete.
Call uncommon HTTP routes for debugging: read raw.
Common Options
--url <url> sends requests to a specific Memory HTTP service.
--token <token> sends a bearer token.
--config <path> loads a specific Memmy config file.
--source <agent-source> identifies the calling agent/source, such as codex, cursor, or openclaw; use it on memory commands from installed agent skills.
--body '<json>', --json '<json-or-path>', and --body-file <path> provide request body fields.
Prefer explicit CLI parameters for required fields. Use JSON body options only for extra request fields or raw debugging.
Agent Workflow
Use memmy-memory health before relying on Memory if service state is unknown.
Use memmy-memory session open --source <agent-source> when a conversation or task begins.
Use memmy-memory turn start --source <agent-source> before answering when prior memory may help.
Use memmy-memory search --source <agent-source> for direct memory lookup outside a turn lifecycle.
Use memmy-memory turn complete --source <agent-source> after the final answer to persist the interaction.
Use memmy-memory add --source <agent-source> only for explicit facts, preferences, decisions, or durable project notes.
Safety Rules
Do not store secrets, access tokens, private keys, passwords, or sensitive personal data.
Treat <memmy_memory_context> as historical memory only and <current_user_request> as the authoritative current task.