What problem does it solve?
Agents often struggle to decide when to query long-term memory versus relying on conversation context, leading to missed user preferences or redundant searches. This Skill defines a clear policy for when and how to consult Zep memory.
Core Features & Use Cases
- Memory Search Policy: Instructs the agent to call
zep_search when turn-scoped system instructions lack shallow Zep recall for the current message.
- Automatic Persistence Awareness: Notes that conversation turns are auto-persisted to Zep, so durable preferences become graph facts without a separate save tool.
- Secret Handling Rules: Prohibits requesting or echoing secrets such as passwords, tokens, payment data, private keys, and OTPs.
- Use Case: When a user mentions a preference between Service A and Service B, the agent checks Zep memory first, then invokes the matching service tool.
Quick Start
Apply this memory policy so the agent searches Zep memory for user preferences whenever the turn-scoped recall section is missing or incomplete.