pickleshell/next-level-agent / skills/mem0-memory
mem0-memory
VerifiedUse optional Mem0 memory tools for focused cross-session recall and short verified durable facts. Use when the user asks to remember or forget something, when resuming work that may need prior context, or after verified progress creates a stable fact worth retaining.
Mem0 Memory
Mem0 is an optional associative-memory layer. Current task context, current repository evidence and documentation, and the NLA private ledger are primary. Mem0 can supply a useful lead, but it is not authoritative live state.
If memory_* tools are absent or a call fails, continue the primary task. When
the user explicitly requested persistence or deletion, say that it could not be
confirmed. Never treat an empty or failed search as proof that a fact is false
or never existed.
Retrieve narrowly
- Use
memory_searchwith a focused query and normallylimit: 3to5. - Do not bulk-dump memory. Avoid
memory_listunless focused search cannot identify a record; if listing is necessary, keep its limit small. - Use
memory_getonly to inspect an identified record exactly. Usememory_historyonly when how that record changed matters. - Recheck paths, commits, repository behavior, and service state in their canonical sources before relying on them.
Bounded retrieval matters especially for 4B models: return only records needed for the current decision.
Store, update, or delete carefully
- Accept only a short, atomic, self-contained, confirmed, durable fact.
- Never store secrets, credentials, tokens, private keys, raw transcripts, large logs, source files, whole documents, guesses, or transient reasoning.
- Before
memory_add, run a precise duplicatememory_searchwith a small limit. Update the matching record withmemory_updateinstead of creating a near-duplicate. - For exact technical facts, identifiers, paths, commits, or explicit wording,
call
memory_addwithinfer: false. - When the user explicitly asks to remember something, write synchronously and
verify it with
memory_getusing the returned ID or a focusedmemory_search. Report honestly if verification fails. - Use
memory_deleteonly for the exact identified record the user asked to forget or that is confirmed obsolete.
The namespace is configured outside the agent and owned by the server/plugin.
Do not invent or pass user_id, namespace, agent_id, or any other scope
override; those are not memory-tool arguments.
Tool surface
Use only the available NLA tools: memory_search, memory_list, memory_get,
memory_add, memory_update, memory_delete, and memory_history.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |