graphiti-memory

Search and record institutional knowledge in Graphiti memory graphs.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Shakudo-io/opencode-skills --skill graphiti-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphiti-memory
Source: https://github.com/Shakudo-io/opencode-skills/tree/main/graphiti-memory
Command: npx skills add https://github.com/Shakudo-io/opencode-skills --skill graphiti-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Graphiti memory enables unified search and persistent recording of institutional knowledge, reducing time spent hunting for context and duplicating solutions.

Core Features & Use Cases

  • Semantic search across Graphiti memory graphs (e.g., shakudo-platform-knowledge, monorepo-project-memory, business-automation-project-memory).
  • Memory recording of verified solutions, architectural decisions, and customer knowledge using add_memory.
  • Use cases include documenting incident diagnoses, capturing design decisions, and linking knowledge to projects.

Quick Start

Query Graphiti to search for relevant knowledge before solving problems and then record verified solutions.

Frequently Asked Questions about graphiti-memory

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

FAQPage Schema
How do I record institutional knowledge and architectural decisions for semantic search?

Semantic search recording captures verified solutions and architectural decisions by using the add_memory function to store context within platform-wide or project-specific memory graphs. This enables persistent retrieval of institutional knowledge.

What is the best way to search a knowledge graph for past incident diagnoses before solving a problem?

Searching a knowledge graph for past incident diagnoses involves using semantic search functions like search_nodes and search_memory_facts to retrieve relevant context from Graphiti memory graphs. This reduces time spent hunting for historical solutions.

Do I need FalkorDB to use Graphiti memory for recording customer insights?

Yes, FalkorDB is required as the backend for Graphiti memory. You must have FalkorDB configured with vector indexes to enable semantic search and memory recording functions for capturing customer insights and architectural decisions.

Can I use semantic memory to document verified solutions across different project memories?

Yes, semantic memory supports documenting verified solutions across multiple project-specific memory graphs like monorepo-project-memory or business-automation-project-memory. You can link knowledge to specific projects and search across them.

How does get_episodes work with Graphiti memory graphs?

The get_episodes function retrieves recorded memory episodes from Graphiti memory graphs, allowing you to access chronological context of previously documented architectural decisions, customer insights, and incident diagnoses.

Why use a knowledge graph for institutional memory instead of standard document search?

A knowledge graph provides semantic search and unified persistent recording, linking architectural decisions and verified solutions across project memories. This reduces duplicating solutions and context hunting compared to standard document search.