graphiti

Store and query time-stamped facts in a temporal knowledge graph.

25|10|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/neuron-one/GODMODE --skill graphiti-neuron-one
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphiti
Source: https://github.com/neuron-one/GODMODE/tree/main/skills/data/graphiti
Command: npx skills add https://github.com/neuron-one/GODMODE --skill graphiti-neuron-one

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Temporal memory that attaches timestamps and expiry to every fact, enabling auditing and evolution tracking of decisions across projects.

Core Features & Use Cases

  • Temporal facts with valid_from and valid_to for each object
  • Track how decisions evolve over time and across projects
  • Use for Stage 3 deep memory and long-term knowledge management; not for simple key-value storage

Quick Start

Create a time-stamped fact entry to begin recording a decision and its validity window.

Frequently Asked Questions about graphiti

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

FAQPage Schema
How do I track decision history with timestamps across multiple projects?

Track decision history with timestamps by storing time-stamped facts in a temporal knowledge graph. This enables auditing and evolution tracking of decisions across multiple projects requiring memory versioning and expiry handling.

What is a temporal knowledge graph for memory management?

A temporal knowledge graph for memory management stores facts with valid_from and valid_to timestamps, supporting temporal queries to audit decision history and track evolution over time. It requires facts to have validity windows for accurate versioning and expiry handling.

When do I need time-aware memory with expiry handling for project tracking?

You need time-aware memory with expiry handling when managing evolving decisions across multiple projects that require versioning and evolution tracking. It is essential for Stage 3 deep memory and long-term knowledge management rather than simple key-value storage.

How do I query expired decisions in a temporal knowledge graph?

Query expired decisions in a temporal knowledge graph by using temporal queries against facts with valid_to timestamps. The graph supports expiry handling to retrieve and audit decisions whose validity windows have ended.

Does graphiti work for simple key-value storage?

Graphiti does not work for simple key-value storage. It is designed for Stage 3 deep memory and long-term knowledge management, requiring facts with valid_from and valid_to fields to support temporal queries and decision evolution tracking.