chroma-memory
Skill191 starsChanged 5 months agoMITView on GitHub
Long-term vector memory for customer conversations. Stores every turn with customer isolation, auto-tags quotes and commitments, enables semantic retrieval across sessions. This skill implements Layer 3 (L3) and Layer 4 (L4) of the 4-layer Anti-Amnesia system: Turns are automatically tagged based on content analysis: All data is partitioned by customer_id (phone number). Queries always include where={"customer_id": ...} to ensure strict tenant isolation.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- workspace/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- b2b-sdr-agentSkill
- delivery-queueSkill
- graphifySkill
- lead-discoverySkill
- quotation-generatorSkill
- sdr-humanizerSkill
- supermemorySkill
- telegram-toolkitSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 38
L3: Every conversation turn → ChromaDB with customer_id isolation + auto-tagging
- Very specific: line 55
All data is partitioned by customer_id (phone number).
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 <query> | Semantic search across conversation history |
chroma:recall <customer_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:statsArchitecture
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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

