Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Enable and configure Moltbot/Clawdbot memory search for persistent context. Use when setting up memory, fixing "goldfish brain," or helping users configure memorySearch in their config. Covers MEMORY.md, daily logs, and vector search setup.
.claude/skills/memory-setup/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-14 | ✗→✓ | ▲ Improved | — | — |
| case-01 | ✗→✓ | ▲ Improved | — | — |
| case-12 | ✗→✓ | ▲ Improved | — | — |
| case-10 | ✗→✓ | ▲ Improved | — | — |
| case-03 | ✗→✓ | ▲ Improved | — | — |
Transform your agent from goldfish to elephant. This skill helps configure persistent memory for Moltbot/Clawdbot.
Add to ~/.clawdbot/clawdbot.json (or moltbot.json):
json{ "memorySearch": { "enabled": true, "provider": "voyage", "sources": ["memory", "sessions"], "indexMode": "hot", "minScore": 0.3, "maxResults": 20 } }
In your workspace, create:
workspace/
├── MEMORY.md # Long-term curated memory
└── memory/
├── logs/ # Daily logs (YYYY-MM-DD.md)
├── projects/ # Project-specific context
├── groups/ # Group chat context
└── system/ # Preferences, setup notesCreate MEMORY.md in workspace root:
markdown# MEMORY.md — Long-Term Memory ## About [User Name] - Key facts, preferences, context ## Active Projects - Project summaries and status ## Decisions & Lessons - Important choices made - Lessons learned ## Preferences - Communication style - Tools and workflows
| Setting | Purpose | Recommended | |---------|---------|-------------| | enabled | Turn on memory search | true | | provider | Embedding provider | "voyage" | | sources | What to index | ["memory", "sessions"] | | indexMode | When to index | "hot" (real-time) | | minScore | Relevance threshold | 0.3 (lower = more results) | | maxResults | Max snippets returned | 20 |
voyage — Voyage AI embeddings (recommended)openai — OpenAI embeddingslocal — Local embeddings (no API needed)memory — MEMORY.md + memory/.md filessessions — Past conversation transcriptsboth — Full context (recommended)Create memory/logs/YYYY-MM-DD.md daily:
markdown# YYYY-MM-DD — Daily Log ## [Time] — [Event/Task] - What happened - Decisions made - Follow-ups needed ## [Time] — [Another Event] - Details
Add to your AGENTS.md for agent behavior:
markdown## Memory Recall Before answering questions about prior work, decisions, dates, people, preferences, or todos: 1. Run memory_search with relevant query 2. Use memory_get to pull specific lines if needed 3. If low confidence after search, say you checked
memorySearch.enabled: true in configclawdbot gateway restartminScore to 0.2 for more resultsmaxResults to 30VOYAGE_API_KEY in environmentOPENAI_API_KEY in environmentlocal provider if no API keys availableTest memory is working:
User: "What do you remember about [past topic]?"
Agent: [Should search memory and return relevant context]If agent has no memory, config isn't applied. Restart gateway.
json{ "memorySearch": { "enabled": true, "provider": "voyage", "sources": ["memory", "sessions"], "indexMode": "hot", "minScore": 0.3, "maxResults": 20 }, "workspace": "/path/to/your/workspace" }
Without memory:
With memory:
Goldfish → Elephant. 🐘
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-14 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-06 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-03 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-15 | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-09 | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-11 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-13 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-02 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-22 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-17 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-08 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-19 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-18 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-16 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-04 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-05 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-20 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-21 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +59 percentage points is the difference between those two pass rates over the 22 comparable cases.
The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.
Other measured skills in the registry, with their headline benchmark lift.