memory-policy

Guides agents on when to search Zep memory for user preferences.

4.9k|651|Updated Apr 29, 2023
One-click install
npx skills add https://github.com/getzep/zep --skill memory-policy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-policy
Source: https://github.com/getzep/zep/tree/main/examples/typescript/eve/agent/skills/memory-policy
Command: npx skills add https://github.com/getzep/zep --skill memory-policy

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about memory-policy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should an agent search Zep memory for user preferences?

Search Zep memory when the turn-scoped system instructions lack shallow recall for the current message or when that section is incomplete. Call zep_search in those cases rather than guessing at user preferences.

Do I need a separate save tool to store preferences in Zep?

No. Conversation turns are auto-persisted to Zep, so durable preferences stated in chat become graph facts automatically without invoking a separate save tool.

How should an agent choose between Service A and Service B tools?

Check Zep memory first for the user's stated preference between the services, then call the matching tool. This avoids asking the user to repeat preferences already stored in the graph.

Can the agent ask users for passwords or tokens?

No. The policy explicitly prohibits requesting or echoing secrets, including passwords, tokens, payment data, private keys, and OTPs, regardless of context.

What are the limitations of turn-scoped Zep recall?

Turn-scoped recall is shallow and may be missing or incomplete for the current message. When that happens, the agent must explicitly call zep_search to retrieve the relevant memory before responding.