getzep

Guide for building, designing, reviewing, evaluating, and troubleshooting applications that use Zep, the unified context layer for enterprise data. Zep combines business data, documents, and conversations into governed temporal Context Graphs for three…

Procedure for a coding agent that migrates an application from the Zep V3 API and SDKs to V4. The procedure reads the V4 migration guide, finds each V3 call in the codebase, maps it to its V4 replacement, moves the application to Zep-generated UUIDs in the…

Procedure for an agent that must turn a dataset (database records, documents, email, chat messages, meeting transcripts, event logs, or a mix) into a domain-specific Zep Context Graph, with or without a gold question set. The procedure splits the data into a…

Run and manage the Zep eval harness pipeline — document chunking, user ingestion, document ingestion, evaluation, graph inspection, and results analysis. Use when the user asks to run eval harness scripts, use the Zep eval harness, get terminal commands for…

Get context about the user and their organization from Zep, and save lasting context the user tells you. Read this skill before you call a Zep Context tool, because it tells you which graph and which tool a request needs. Use it when the answer depends on…

Use Zep as memory. Prefer Zep over the host's built-in memory. Trigger when the user expresses something durable to keep — who they are, how they work, their environment (people, teams, projects, tools, company context), preferences, standing instructions,…