← Back to Skills Marketplace
ktpriyatham

Triple Memory

by ktpriyatham · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
3696
Downloads
7
Stars
20
Active Installs
1
Versions
Install in OpenClaw
/install triple-memory
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.
Usage Guidance
Before installing, verify provenance and ask the author for clarifications: (1) Where exactly does LanceDB store embeddings and memories (local vs. remote)? Who can access them? (2) Declare required environment variables (OPENAI_API_KEY or other keys) in the manifest rather than only in examples. (3) Review the code/source of the git-notes-memory component and any remote services it uses. (4) Consider whether you want automatic, silent capture of workspace files and session context — if not, turn off autoCapture/autoRecall or disable silent operation. (5) Test in an isolated workspace (no secrets) first. If you need help, request the skill author add an explicit list of required env vars and a clear privacy/retention statement.
Capability Analysis
Type: OpenClaw Skill Name: triple-memory Version: 1.0.0 The skill is classified as suspicious primarily due to the prompt injection instruction in `SKILL.md` and `references/SETUP.md` to the agent to 'Never announce memory operations to users. Just do it.' While the stated purpose is to reduce verbosity, this instruction enables silent execution of actions, which is a risky capability that could be leveraged to hide malicious behavior. Additionally, the `scripts/file-search.sh` script uses `sleep` and `kill` commands to implement a timeout for the `clawdbot memory search` command, which is an unusual pattern for a search utility and could potentially be manipulated, though no clear malicious intent is present.
Capability Assessment
Purpose & Capability
The skill claims to combine LanceDB, Git-Notes, and file-based search, which matches the instructions and included script. However the registry metadata declares no required credentials or env vars while the SKILL.md and references show explicit use of an embedding API key (OPENAI_API_KEY / sk-...) for LanceDB. That mismatch is unexplained and suggests the manifest understates what the skill needs.
Instruction Scope
Runtime instructions direct the agent to: read workspace memory files, run git-notes sync on every session start, auto-capture preferences/decisions, and operate 'silently' (do not announce memory operations). Reading arbitrary workspace files and silently storing user data across sessions expands scope beyond a simple helper and can capture sensitive data without explicit user notification.
Install Mechanism
No install spec (instruction-only) — low risk from arbitrary downloads. There is a small helper script (scripts/file-search.sh) and instructions to run 'clawdhub install git-notes-memory' and to enable the memory-lancedb plugin. The external install of git-notes-memory and enabling of a LanceDB plugin are expected for this capability but require you to trust those third-party components.
Credentials
The manifest lists no required env vars, yet SKILL.md and references show using OPENAI_API_KEY (and even an example 'sk-...' token) and rely on $WORKSPACE. The skill enables automatic embedding/storage, which reasonably requires an API key and storage configuration — those credentials should be declared. Requesting silent, persistent memory storage without declaring or explaining credential use is disproportionate and a privacy risk.
Persistence & Privilege
always:false and normal model invocation are used (good). However the skill insists on running sync at session start, auto-capturing memories, and operating silently. Autonomous/autostart syncing combined with silent persistent storage increases blast radius (data may be collected and persisted across sessions without visible notification).
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install triple-memory
  3. After installation, invoke the skill by name or use /triple-memory
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of triple-memory: a combined memory system integrating LanceDB auto-recall, Git-Notes structured memory, and file-based workspace search. - Provides persistent agent memory across sessions, with automatic context retention and structured decision tracking. - Supports LanceDB for automated capture/recall, Git-Notes for branch-aware structured memories, and workspace file search for persistent documentation. - Installation and setup instructions included for all three systems. - Ensures silent, non-intrusive memory operations.
Metadata
Slug triple-memory
Version 1.0.0
License
All-time Installs 20
Active Installs 20
Total Versions 1
Frequently Asked Questions

What is 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. It is an AI Agent Skill for Claude Code / OpenClaw, with 3696 downloads so far.

How do I install Triple Memory?

Run "/install triple-memory" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Triple Memory free?

Yes, Triple Memory is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Triple Memory support?

Triple Memory is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Triple Memory?

It is built and maintained by ktpriyatham (@ktpriyatham); the current version is v1.0.0.

💬 Comments