
Memory Setup
- 1.6k installs
- 635 repo stars
- Updated March 7, 2026
- sundial-org/awesome-openclaw-skills
A configured Moltbot/Clawdbot agent that searches vector-indexed memory (MEMORY.md, logs, sessions) before answering questions about prior work, decisions, preferences, or project history.
About
Memory Setup enables Moltbot and Clawdbot agents to maintain persistent context through vector-based memory search across MEMORY.md files, daily logs, and past sessions. Developers use this skill when deploying agents that need to recall prior conversations, decisions, project history, and user preferences without retraining. The workflow covers enabling memorySearch in config, structuring memory directories (MEMORY.md, logs/, projects/, groups/, system/), choosing embedding providers (Voyage, OpenAI, or local), and tuning retrieval parameters (minScore, maxResults). Critical for agents that serve as persistent assistants rather than stateless chat interfaces.
- Configure memorySearch in clawdbot.json with provider selection (Voyage/OpenAI/local) and tuning (minScore 0.2-0.3, maxR
- Create MEMORY.md root file for curated long-term context: user facts, active projects, decisions, preferences
- Structure memory/ subdirectories: logs/ (daily YYYY-MM-DD.md), projects/, groups/, system/ for organized indexing
- Choose real-time indexing (indexMode: hot) and source scope (memory, sessions, or both) based on retrieval needs
- Add memory_search and memory_get agent instructions to AGENTS.md to recall context before answering prior-work questions
Memory Setup by the numbers
- 1,559 all-time installs (skills.sh)
- +44 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #773 of 16,659 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
memory-setup capabilities & compatibility
Free (local provider) or per-token API cost (Voyage/OpenAI)
- Capabilities
- configure vector search · manage memory structure · tune embedding retrieval · enable persistent context · structure daily logs
- Works with
- openai
- Use cases
- documentation · project management · memory
- Platforms
- macOS · Windows · Linux · WSL
- Runs
- Runs locally
- Pricing
- Free
npx skills add https://github.com/sundial-org/awesome-openclaw-skills --skill memory-setupAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.6k |
|---|---|
| repo stars | ★ 635 |
| Security audit | 3 / 3 scanners passed |
| Last updated | March 7, 2026 |
| Repository | sundial-org/awesome-openclaw-skills ↗ |
What it does
Configure persistent memory and vector search for Moltbot/Clawdbot agents to retain context across conversations.
Who is it for?
Building persistent assistants, long-running projects, user preference learning, decision tracking, multi-session continuity, knowledge retention across conversations.
Skip if: Stateless chat endpoints, single-turn interactions, agents without file access, systems without embedding API access (unless using local provider).
When should I use this skill?
Setting up Moltbot/Clawdbot for the first time, fixing agent that forgets context, enabling memory search on existing agent, tuning retrieval quality.
What you get
Agent recalls past conversations, knows user preferences, tracks project history, and maintains relationship continuity by indexing and searching memory files via vector embeddings.
- memorySearch config in clawdbot.json or moltbot.json
- MEMORY.md file in workspace root
- memory/ directory with logs/, projects/, groups/, system/ subdirs
By the numbers
- Config provides 6 tunable parameters: enabled, provider, sources, indexMode, minScore, maxResults
- Supports 3 embedding providers: Voyage, OpenAI, local
- Default minScore 0.3, maxResults 20; range minScore 0.2-0.5 for tuning
Files
Memory Setup Skill
Transform your agent from goldfish to elephant. This skill helps configure persistent memory for Moltbot/Clawdbot.
Quick Setup
1. Enable Memory Search in Config
Add to ~/.clawdbot/clawdbot.json (or moltbot.json):
{
"memorySearch": {
"enabled": true,
"provider": "voyage",
"sources": ["memory", "sessions"],
"indexMode": "hot",
"minScore": 0.3,
"maxResults": 20
}
}2. Create Memory Structure
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 notes3. Initialize MEMORY.md
Create MEMORY.md in workspace root:
# 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 workflowsConfig Options Explained
| 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 |
Provider Options
voyage— Voyage AI embeddings (recommended)openai— OpenAI embeddingslocal— Local embeddings (no API needed)
Source Options
memory— MEMORY.md + memory/*.md filessessions— Past conversation transcriptsboth— Full context (recommended)
Daily Log Format
Create memory/logs/YYYY-MM-DD.md daily:
# YYYY-MM-DD — Daily Log
## [Time] — [Event/Task]
- What happened
- Decisions made
- Follow-ups needed
## [Time] — [Another Event]
- DetailsAgent Instructions (AGENTS.md)
Add to your AGENTS.md for agent behavior:
## 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 checkedTroubleshooting
Memory search not working?
1. Check memorySearch.enabled: true in config 2. Verify MEMORY.md exists in workspace root 3. Restart gateway: clawdbot gateway restart
Results not relevant?
- Lower
minScoreto0.2for more results - Increase
maxResultsto30 - Check that memory files have meaningful content
Provider errors?
- Voyage: Set
VOYAGE_API_KEYin environment - OpenAI: Set
OPENAI_API_KEYin environment - Use
localprovider if no API keys available
Verification
Test 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.
Full Config Example
{
"memorySearch": {
"enabled": true,
"provider": "voyage",
"sources": ["memory", "sessions"],
"indexMode": "hot",
"minScore": 0.3,
"maxResults": 20
},
"workspace": "/path/to/your/workspace"
}Why This Matters
Without memory:
- Agent forgets everything between sessions
- Repeats questions, loses context
- No continuity on projects
With memory:
- Recalls past conversations
- Knows your preferences
- Tracks project history
- Builds relationship over time
Goldfish → Elephant. 🐘
Related skills
Forks & variants (1)
Memory Setup has 1 known copy in the catalog totaling 107 installs. They canonicalize to this original listing.
- skills.volces.com - 107 installs
How it compares
Use memory-setup for self-hosted Clawdbot or Moltbot vector memory; pick claude-mem or similar skills when memory attaches to a different agent runtime.
FAQ
What is the difference between Voyage, OpenAI, and local embedding providers?
Voyage and OpenAI require API keys but offer high-quality embeddings. Local provider needs no keys but runs on-device with lower quality. Choose Voyage (recommended), OpenAI (if already using), or local (offline/budget).
How do I fix memory search returning irrelevant results?
Lower minScore from 0.3 to 0.2, increase maxResults to 30, and ensure memory files have meaningful content. Restart gateway after config changes.
What goes in MEMORY.md vs. daily logs?
MEMORY.md holds curated long-term facts (user preferences, key decisions, project summaries). Daily logs (memory/logs/YYYY-MM-DD.md) capture events, tasks, and follow-ups by timestamp.
Is Memory Setup safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.