← Back to Skills Marketplace
Chroma Memory
by
iPythoning
· GitHub ↗
· v1.0.1
· MIT-0
153
Downloads
0
Stars
2
Active Installs
2
Versions
Install in OpenClaw
/install chroma-memory
Description
Stores and semantically retrieves per-turn customer conversation data with auto-tagging and customer isolation using ChromaDB.
README (SKILL.md)
chroma-memory — Per-Turn Conversation Memory with ChromaDB
Long-term vector memory for customer conversations. Stores every turn with customer isolation, auto-tags quotes and commitments, enables semantic retrieval across sessions.
Commands
| Command | Description |
|---|---|
chroma:store |
Store a conversation turn (auto-called after each turn) |
chroma:search \x3Cquery> |
Semantic search across conversation history |
chroma:recall \x3Ccustomer_id> |
Recall recent history for a returning customer |
chroma:snapshot |
Store daily CRM snapshot as fallback (L4) |
chroma:stats |
Show storage statistics |
Usage
# Store a turn (normally auto-triggered by hook)
chroma:store --customer "+971501234567" --turn 5 --user "What's the price for 500 units?" --agent "Let me prepare a detailed quote..." --stage qualifying --topic pricing
# Search history
chroma:search "Dubai customer pricing discussion" --customer "+971501234567" --limit 5
# Recall for returning customer (auto-triggered when gap > 7 days)
chroma:recall "+971501234567" --limit 10
# Daily CRM snapshot (triggered by HEARTBEAT #12)
chroma:snapshot
# Stats
chroma:stats
Architecture
This skill implements Layer 3 (L3) and Layer 4 (L4) of the 4-layer Anti-Amnesia system:
- L3: Every conversation turn → ChromaDB with customer_id isolation + auto-tagging
- L4: Daily CRM snapshot → ChromaDB as disaster recovery fallback
Auto-Tagging
Turns are automatically tagged based on content analysis:
| Tag | Trigger |
|---|---|
has_quote |
Price/cost/quote discussed |
has_commitment |
Promise made by either party |
has_objection |
Customer objection detected |
has_order |
Order/purchase confirmed |
has_sample |
Sample request discussed |
Customer Isolation
All data is partitioned by customer_id (phone number). Queries always include where={"customer_id": ...} to ensure strict tenant isolation.
Dependencies
chromadbskill (vector database, install via ClawHub)- OpenClaw Gateway with session-memory hook enabled
Usage Guidance
The core issue is mismatch: the skill promises ChromaDB-backed semantic vector memory but the bundled code implements only local JSON storage and lexical ranking. Before installing, decide whether you want a local file-based memory (this code) or true ChromaDB/vector embeddings. If you accept local storage, confirm where files will be written (OPENCLAW_HOME or HOME), whether data-at-rest is encrypted, retention/cleanup policies, and whether phone numbers/PII are acceptable to store on disk. If you expect a ChromaDB integration, ask the publisher to provide the real connector or remove the misleading claims. Also note the script requires Node.js to run (not declared) — inspect and test the code in a sandbox with non-production data first.
Capability Tags
Capability Assessment
Purpose & Capability
SKILL.md and description claim ChromaDB integration and semantic (vector) retrieval; the provided chroma.mjs contains no network/DB calls, no use of chromadb or embeddings — it stores JSON files under ~/.openclaw/memory/chroma and uses simple lexical overlap + heuristics for search. The declared dependency on a 'chromadb' skill and the ChromaDB branding are therefore misleading.
Instruction Scope
Runtime instructions describe 'auto-called' hooks, tenant isolation via where filters, and semantic searches. The code is a standalone Node CLI that reads/writes local JSON files and does not implement semantic vector search or any hook integration. SKILL.md references HEARTBEAT triggers and OpenClaw Gateway behavior that are not visible in the code.
Install Mechanism
There is no install spec (instruction-only), which is low risk. However, the package includes a Node .mjs script but the skill metadata lists no required binaries; 'node' is effectively required to run chroma.mjs but isn't declared. Nothing in the install path downloads remote code or runs network installers.
Credentials
The skill declares no required secrets or env vars. The code reads OPENCLAW_HOME or HOME and optionally CRM_SNAPSHOT_DATA (used for snapshot piping) — these env vars are not documented in requires.env. None are sensitive credentials, but CRM_SNAPSHOT_DATA could contain bulk CRM data and is not flagged as a required/optional env var in the metadata.
Persistence & Privilege
always:false and normal invocation. The code writes persistent files into the user's HOME (or OPENCLAW_HOME) under a .openclaw/memory/chroma path and will create directories and many JSON files. It does not modify other skills or system-wide settings, but it does persist potentially sensitive conversation data on disk.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install chroma-memory - After installation, invoke the skill by name or use
/chroma-memory - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
chroma-memory 1.0.1
- Documentation updates only: SKILL.md reformatted, with no changes to commands, features, or usage.
- No functional changes to the core skill logic.
v1.0.0
Initial publish from b2b-sdr-agent-template v3.3.1
Metadata
Frequently Asked Questions
What is Chroma Memory?
Stores and semantically retrieves per-turn customer conversation data with auto-tagging and customer isolation using ChromaDB. It is an AI Agent Skill for Claude Code / OpenClaw, with 153 downloads so far.
How do I install Chroma Memory?
Run "/install chroma-memory" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Chroma Memory free?
Yes, Chroma Memory is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Chroma Memory support?
Chroma Memory is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Chroma Memory?
It is built and maintained by iPythoning (@ipythoning); the current version is v1.0.1.
More Skills