c95ffa03c5
- Add 4 missing skills: chromedp-alpine-container, claude-memory-api, openclaw-custom-model-provider, webrtc-turn-shared-secret - Add 9 custom agents: sre, dba, devops-engineer, platform-engineer, security-engineer, network-engineer, observability-engineer, home-automation-engineer, cluster-health-checker - Add openclaw-install.sh: standalone script to clone dotfiles and install skills/agents/hooks/settings to OpenClaw's home directory Replaces the cc-config NFS volume + sync.sh approach
1.4 KiB
1.4 KiB
| name | description |
|---|---|
| claude-memory-api | Store and recall persistent memories using the memory-tool CLI. Use when the user asks to remember something, recall a previous memory, or when you want to persist knowledge across sessions. |
Claude Memory API
You have access to a persistent memory system via the memory-tool CLI command.
When to Use
- User says "remember this", "save this", "note that..."
- User asks "do you remember...", "what do you know about...", "recall..."
- You discover important facts worth persisting (user preferences, project patterns, debugging insights)
- You need to check if you already know something before asking the user
Commands
Store a memory
memory-tool store "content to remember" --category <category> --tags "tag1,tag2"
Categories: facts, preferences, patterns, debugging, architecture
Recall memories (semantic search)
memory-tool recall "search query"
List all memories
memory-tool list
memory-tool list --category facts
Delete a memory
memory-tool delete <memory-id>
Guidelines
- Always
recallbefore storing to avoid duplicates - Use specific, descriptive content — memories should be self-contained
- Choose the most relevant category
- Add tags for better recall later
- When the user says "remember X", store it immediately and confirm