How do I install the Triple Memory skill?

Run npx skillmds@latest add thinkfleetai/triple-memory in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Triple Memory safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Triple Memory?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Triple Memory free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Triple Memory?

thinkfleetai (@thinkfleetai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Triple Memory by thinkfleetai — Agent Skill

Name: Triple Memory
Author: thinkfleetai

Triple Memory

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.

thinkfleetai a7365be 3.7 KB Updated Sep 17, 2026

File contents

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

thinkfleet-hub 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

Flag	Level	When to Use
`-i c`	Critical	"always remember", explicit preferences
`-i h`	High	Decisions, corrections, preferences
`-i n`	Normal	General information
`-i l`	Low	Temporary notes

When to Use Each System

System	Use For
LanceDB	Conversation context, auto-retrieval
Git-Notes	Structured decisions, searchable by entity/tag
File Search	Workspace 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)

---name: triple-memorydescription: 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.---# Triple Memory SystemA 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```json{ "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```bashthinkfleet-hub install git-notes-memory```### Create File Search ScriptCopy `scripts/file-search.sh` to your workspace.## Usage### Session Start (Always)```bashpython3 skills/git-notes-memory/memory.py -p $WORKSPACE sync --start```### Store Important Decisions```bashpython3 skills/git-notes-memory/memory.py -p $WORKSPACE remember \ '{"decision": "Use PostgreSQL", "reason": "Team expertise"}' \ -t architecture,database -i h```### Search Workspace Files```bash./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| Flag | Level | When to Use ||------|-------|-------------|| `-i c` | Critical | "always remember", explicit preferences || `-i h` | High | Decisions, corrections, preferences || `-i n` | Normal | General information || `-i l` | Low | Temporary notes |## When to Use Each System| System | Use For ||--------|---------|| **LanceDB** | Conversation context, auto-retrieval || **Git-Notes** | Structured decisions, searchable by entity/tag || **File Search** | Workspace 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 OperationNever announce memory operations to users. Just do it:- ❌ "I'll remember this"- ❌ "Saving to memory"- ✅ (silently store and continue)

Frequently asked questions