skills$openclaw/triple-memory
ktpriyatham614ā˜…

by ktpriyatham

triple-memory – OpenClaw Skill

triple-memory is an OpenClaw Skills integration for data analytics workflows. Complete memory system combining LanceDB auto-recall, Git-Notes structured memory, and file-based workspace search. Use when setting up comprehensive agent memory, when you need persistent context across sessions, or when managing decisions/preferences/tasks with multiple memory backends working together.

614 stars629 forksSecurity L1
Updated Feb 7, 2026Created Feb 7, 2026data analytics

Skill Snapshot

nametriple-memory
descriptionComplete memory system combining LanceDB auto-recall, Git-Notes structured memory, and file-based workspace search. Use when setting up comprehensive agent memory, when you need persistent context across sessions, or when managing decisions/preferences/tasks with multiple memory backends working together. OpenClaw Skills integration.
ownerktpriyatham
repositoryktpriyatham/triple-memory
languageMarkdown
licenseMIT
topics
securityL1
installopenclaw add @ktpriyatham/triple-memory
last updatedFeb 7, 2026

Maintainer

ktpriyatham

ktpriyatham

Maintains triple-memory in the OpenClaw Skills directory.

View GitHub profile
File Explorer
6 files
.
references
SETUP.md
1.4 KB
scripts
file-search.sh
570 B
_meta.json
283 B
SKILL.md
3.9 KB
SKILL.md

name: triple-memory version: 1.0.0 description: Complete memory system combining LanceDB auto-recall, Git-Notes structured memory, and file-based workspace search. Use when setting up comprehensive agent memory, when you need persistent context across sessions, or when managing decisions/preferences/tasks with multiple memory backends working together. metadata: clawdbot: emoji: "🧠" requires: plugins: - memory-lancedb skills: - git-notes-memory

Triple Memory System

A comprehensive memory architecture combining three complementary systems for maximum context retention across sessions.

Architecture Overview

User Message
     ↓
[LanceDB auto-recall] → injects relevant conversation memories
     ↓
Agent responds (using all 3 systems)
     ↓
[LanceDB auto-capture] → stores preferences/decisions automatically
     ↓
[Git-Notes] → structured decisions with entity extraction
     ↓
[File updates] → persistent workspace docs

The Three Systems

1. LanceDB (Conversation Memory)

  • Auto-recall: Relevant memories injected before each response
  • Auto-capture: Preferences/decisions/facts stored automatically
  • Tools: memory_recall, memory_store, memory_forget
  • Triggers: "remember", "prefer", "my X is", "I like/hate/want"

2. Git-Notes Memory (Structured, Local)

  • Branch-aware: Memories isolated per git branch
  • Entity extraction: Auto-extracts topics, names, concepts
  • Importance levels: critical, high, normal, low
  • No external API calls

3. File Search (Workspace)

  • Searches: MEMORY.md, memory/*.md, any workspace file
  • Script: scripts/file-search.sh

Setup

Enable LanceDB Plugin

{
  "plugins": {
    "slots": { "memory": "memory-lancedb" },
    "entries": {
      "memory-lancedb": {
        "enabled": true,
        "config": {
          "embedding": { "apiKey": "${OPENAI_API_KEY}", "model": "text-embedding-3-small" },
          "autoRecall": true,
          "autoCapture": true
        }
      }
    }
  }
}

Install Git-Notes Memory

clawdhub install git-notes-memory

Create File Search Script

Copy scripts/file-search.sh to your workspace.

Usage

Session Start (Always)

python3 skills/git-notes-memory/memory.py -p $WORKSPACE sync --start

Store Important Decisions

python3 skills/git-notes-memory/memory.py -p $WORKSPACE remember \
  '{"decision": "Use PostgreSQL", "reason": "Team expertise"}' \
  -t architecture,database -i h

Search Workspace Files

./scripts/file-search.sh "database config" 5

Conversation Memory (Automatic)

LanceDB handles this automatically. Manual tools:

  • memory_recall "query" - search conversation memory
  • memory_store "text" - manually store something
  • memory_forget - delete memories (GDPR)

Importance Levels

FlagLevelWhen to Use
-i cCritical"always remember", explicit preferences
-i hHighDecisions, corrections, preferences
-i nNormalGeneral information
-i lLowTemporary notes

When to Use Each System

SystemUse For
LanceDBConversation context, auto-retrieval
Git-NotesStructured decisions, searchable by entity/tag
File SearchWorkspace docs, daily logs, MEMORY.md

File Structure

workspace/
ā”œā”€ā”€ MEMORY.md              # Long-term curated memory
ā”œā”€ā”€ memory/
│   ā”œā”€ā”€ active-context.md  # Current session state
│   └── YYYY-MM-DD.md      # Daily logs
ā”œā”€ā”€ scripts/
│   └── file-search.sh     # Workspace search
└── skills/
    └── git-notes-memory/  # Structured memory

Silent Operation

Never announce memory operations to users. Just do it:

  • āŒ "I'll remember this"
  • āŒ "Saving to memory"
  • āœ… (silently store and continue)
README.md

No README available.

Permissions & Security

Security level L1: Low-risk skills with minimal permissions. Review inputs and outputs before running in production.

Requirements

  • OpenClaw CLI installed and configured.
  • Language: Markdown
  • License: MIT
  • Topics:

FAQ

How do I install triple-memory?

Run openclaw add @ktpriyatham/triple-memory in your terminal. This installs triple-memory into your OpenClaw Skills catalog.

Does this skill run locally or in the cloud?

OpenClaw Skills execute locally by default. Review the SKILL.md and permissions before running any skill.

Where can I verify the source code?

The source repository is available at https://github.com/openclaw/skills/tree/main/skills/ktpriyatham/triple-memory. Review commits and README documentation before installing.