Memory Setup (Jack)

v1.0.0

Enable and configure Moltbot/Clawdbot memory search for persistent context. Use when setting up memory, fixing "goldfish brain," or helping users configure m...

0· 170·1 current·1 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for jackwang2999/memory-setup-jack.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Memory Setup (Jack)" (jackwang2999/memory-setup-jack) from ClawHub.
Skill page: https://clawhub.ai/jackwang2999/memory-setup-jack
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install memory-setup-jack

ClawHub CLI

Package manager switcher

npx clawhub@latest install memory-setup-jack
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the instructions: the SKILL.md explains enabling memorySearch, creating MEMORY.md and memory/ folders, and configuring embedding providers—all coherent with a memory-setup utility.
Instruction Scope
Instructions focus on editing the agent config (~/.clawdbot/clawdbot.json or moltbot.json), creating workspace files, and restarting the agent gateway. They do not instruct reading or exfiltrating unrelated system files or contacting unexpected endpoints.
Install Mechanism
No install spec or code files are present; this is instruction-only so nothing is downloaded or written by the skill itself.
Credentials
The skill metadata declares no required env vars, but the doc mentions VOYAGE_API_KEY and OPENAI_API_KEY as provider-specific requirements (in troubleshooting). This is proportionate for embedding providers, but the metadata could explicitly list them as optional to avoid confusion.
Persistence & Privilege
Skill is not force-included (always:false) and does not request persistent system-wide privileges; it instructs the user to modify their agent's own config files and to restart the gateway, which is expected for this task.
Assessment
This skill is a how-to for enabling and configuring your agent's memory and appears internally consistent. Before applying: back up your existing ~/.clawdbot/moltbot config, review any memory files you create for sensitive data (they will be indexed), and prefer the local provider if you don't want to supply external API keys. Note the doc mentions VOYAGE_API_KEY and OPENAI_API_KEY for external embedding providers—only provide those keys if you trust the provider and understand where embeddings/requests are sent.

Like a lobster shell, security has layers — review code before you run it.

latestvk97452rc2z19pvn3826ypz42y183awar
170downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

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

SettingPurposeRecommended
enabledTurn on memory searchtrue
providerEmbedding provider"voyage"
sourcesWhat to index["memory", "sessions"]
indexModeWhen to index"hot" (real-time)
minScoreRelevance threshold0.3 (lower = more results)
maxResultsMax snippets returned20

Provider Options

  • voyage — Voyage AI embeddings (recommended)
  • openai — OpenAI embeddings
  • local — Local embeddings (no API needed)

Source Options

  • memory — MEMORY.md + memory/*.md files
  • sessions — Past conversation transcripts
  • both — 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?

  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 minScore to 0.2 for more results
  • Increase maxResults to 30
  • Check that memory files have meaningful content

Provider errors?

  • Voyage: Set VOYAGE_API_KEY in environment
  • OpenAI: Set OPENAI_API_KEY in environment
  • Use local provider 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. 🐘

Comments

Loading comments...