memory-setup▌
sundial-org/awesome-openclaw-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Configure persistent memory search for Moltbot/Clawdbot agents to retain context across sessions.
- ›Add memorySearch config block with provider (Voyage, OpenAI, or local), sources (memory files and/or sessions), and relevance thresholds
- ›Create a workspace structure with MEMORY.md for curated long-term facts and memory/logs/ for daily timestamped logs
- ›Supports three embedding providers; Voyage recommended but local option available without API keys
- ›Includes troubleshooting for common
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 notes
3. 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 workflows
Config 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]
- Details
Agent 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 checked
Troubleshooting
Memory search not working?
- Check
memorySearch.enabled: truein config - Verify MEMORY.md exists in workspace root
- 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. 🐘
How to use memory-setup on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add memory-setup
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches memory-setup from GitHub repository sundial-org/awesome-openclaw-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate memory-setup. Access the skill through slash commands (e.g., /memory-setup) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★72 reviews- ★★★★★Camila Liu· Dec 28, 2024
memory-setup has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Carlos Wang· Dec 24, 2024
memory-setup fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ganesh Mohane· Dec 16, 2024
Registry listing for memory-setup matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Camila Wang· Dec 12, 2024
memory-setup has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Nikhil Taylor· Nov 19, 2024
Solid pick for teams standardizing on skills: memory-setup is focused, and the summary matches what you get after install.
- ★★★★★Aarav Srinivasan· Nov 19, 2024
We added memory-setup from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Anika Jackson· Nov 15, 2024
memory-setup is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Sakshi Patil· Nov 7, 2024
Keeps context tight: memory-setup is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Camila Li· Nov 3, 2024
memory-setup reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Omar Harris· Nov 3, 2024
Solid pick for teams standardizing on skills: memory-setup is focused, and the summary matches what you get after install.
showing 1-10 of 72