Skill

automem

Manages persistent memories using AutoMem OpenClaw plugin tools: store, recall, update, delete, associate, and check health for project decisions, preferences, and context.

developer-tools

npx claudepluginhub joshuarweaver/cascade-ai-ml-agents-misc-1 --plugin verygoodplugins-mcp-automem

Tool Access

This skill uses the workspace's default tool permissions.

Preview

SKILL.md

Similar Skills

memora

380

Manages persistent semantic memory across sessions: store/retrieve knowledge/TODOs/issues, hybrid semantic search, hierarchy/tags organization, and maintenance tools.

memora

mem0-codex

52.1k

Integrates Mem0 persistent memory for Claude Code tasks using MCP tools. Retrieves relevant memories on new tasks, stores learnings like decisions and strategies, captures session states.

mem0

using-forgetful-memory

PROACTIVELY query Forgetful MCP (mcp__forgetful__* tools) when starting work on any project, when user references past decisions or patterns, when implementing features that may have been solved before, or when needing context about preferences. Save important decisions, patterns, and architectural insights to memory.

1 file

context-hub-plugin

Stats

Stars47

Forks11

Last CommitApr 25, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

AutoMem

Use the native AutoMem tools exposed by the AutoMem plugin.

Natural language mappings

remember ... or store this -> call automem_store_memory

what do you know about ... or recall ... -> call automem_recall_memory

update memory ... -> call automem_update_memory

delete memory ... -> recall first when needed, then call automem_delete_memory

link these memories ... -> call automem_associate_memories

is memory healthy? -> call automem_check_health

Slash command behavior

Treat /automem remember ..., /automem recall ..., /automem update ..., and /automem delete ... as direct requests to use the matching AutoMem tool flow above.

Rules

Recall first for prior decisions, preferences, ongoing projects, and debugging history.

Store durable outcomes: decisions, bug fixes, patterns, preferences, and important context.

Keep content compact: Brief title. Context and details. Impact/outcome.

If deletion is ambiguous, recall candidates first and ask for confirmation with ids before deleting.

Use memory-core alongside AutoMem when file-backed workspace memory is helpful. It complements AutoMem; it is not a replacement.