memory-setup
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.
Security Assessment
About memory-setup
memory-setup helps users configure persistent memory for the Moltbot/Clawdbot agent so it stops behaving like a goldfish and retains context across sessions. It addresses the common problem of an agent forgetting prior conversations, repeating questions, and losing continuity on projects, by enabling memory search and a structured on-disk memory layout.
The skill walks through enabling a memorySearch block in the agent config (~/.clawdbot/clawdbot.json or moltbot.json) with options for provider, sources, index mode, minimum relevance score, and max results; creating a workspace memory structure (a curated MEMORY.md plus a memory/ tree for daily logs, projects, groups, and system notes); and initializing MEMORY.md and daily log templates. It documents each config setting with recommended values, offers embedding-provider choices (Voyage, OpenAI, or a local no-API option), and provides AGENTS.md instructions telling the agent to run memory_search and memory_get before answering questions about prior work. It also includes troubleshooting for search not working, irrelevant results, and provider errors, plus a gateway restart step and a verification test.
Target users are Moltbot/Clawdbot operators who want durable, searchable long-term memory and better project continuity. The skill only edits local config and creates local markdown files, and it references embedding API keys (VOYAGE_API_KEY, OPENAI_API_KEY) as standard environment-variable setup with a local no-key alternative. There is no data exfiltration or destructive behavior, so it is a benign configuration helper.
FAQ
What does this skill set up?
It enables the memorySearch feature in the Moltbot/Clawdbot config and creates a workspace memory structure (MEMORY.md plus a memory/ tree of logs, projects, groups, and system notes) for persistent, searchable context.
Which embedding providers are supported?
Voyage AI (recommended), OpenAI, or a local provider that needs no API key. Voyage and OpenAI use VOYAGE_API_KEY or OPENAI_API_KEY in the environment.
What config values does it recommend?
Enabled true, provider voyage, sources memory and sessions, hot (real-time) index mode, a minScore around 0.3, and maxResults around 20, all adjustable for more or fewer results.
Why isn't memory working after setup?
Common causes are memorySearch.enabled not set to true, a missing MEMORY.md in the workspace root, or the gateway not restarted — the skill includes a clawdbot gateway restart step and a verification test.
Do I have to use a cloud embedding service?
No. You can select the local provider to run embeddings without any API key if you prefer to avoid external services.
Install memory-setup
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
sundial-org/awesome-openclaw-skills