Memory Setup
v1.0.0Enable 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.
⭐ 115· 33.7k·399 current·420 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (memory setup for Moltbot/Clawdbot) aligns with the instructions: editing clawdbot config, creating MEMORY.md and memory/ files, choosing an embedding provider, and restarting the gateway. All requested actions are plausible for this purpose.
Instruction Scope
SKILL.md stays on-topic: it tells the operator to add config entries, create workspace memory files, run memory_search/memory_get, and restart the gateway. It does instruct the agent/operator to create files that may contain sensitive personal data (MEMORY.md, daily logs), which is expected for a memory feature but worth noting.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so there is no installer behavior to review and nothing is automatically written or executed by an installer.
Credentials
The registry metadata declares no required environment variables, but the SKILL.md references VOYAGE_API_KEY and OPENAI_API_KEY when using external providers. Requesting API keys is proportionate to using external embedding services, but the metadata omission is an inconsistency and the instructions access env-based credentials that were not declared.
Persistence & Privilege
The skill modifies user configuration files and asks the operator to create persistent memory files (expected). It does not request always:true or other elevated platform privileges; it does not modify other skills or system-wide settings beyond the user's own config/workspace.
Assessment
This skill appears to do what it says: help enable/configure memory for Moltbot/Clawdbot. Before installing/using it, consider the following:
- API keys: SKILL.md mentions VOYAGE_API_KEY and OPENAI_API_KEY if you choose those providers, but the skill metadata does not list required env vars. Expect to supply those keys yourself if you pick an external provider. Verify the provider (Voyage) before giving it an API key.
- Sensitive data: MEMORY.md and daily logs will contain persistent personal or project information. Treat them as sensitive—store them in a protected workspace, consider encryption, and avoid putting secrets or credentials in those files.
- Local alternative: If privacy is a concern, use the 'local' provider option (no external API keys) as recommended in the doc.
- Operational steps: The instructions include restarting the gateway (clawdbot gateway restart). That requires appropriate permissions; confirm you understand what that command does in your environment before running it.
- Provenance: The skill has no homepage or source listed. If you need higher assurance, ask the publisher for source code or provenance and for the rationale behind the missing env-var declarations.
Confidence is medium because this is an instruction-only skill (no code to analyze) and the only notable issue is the metadata vs. instructions mismatch about environment variables. If the publisher supplied explicit required env vars or source code, confidence could increase.Like a lobster shell, security has layers — review code before you run it.
latestvk970bss9k60ngp8sz0kj2kya35803923
License
MIT-0
Free to use, modify, and redistribute. No attribution required.