Helps agents choose the right agentmemory tool through MCP, a protocol for connecting agents to tools. It explains tool roles and points to parameter references for saving, retrieving, organizing, and maintaining stored knowledge.
Map of every agentmemory MCP tool, what each does, and its parameters. Use when choosing which memory tool to call, when a tool name or argument is unclear, or when answering what agentmemory can do via MCP.
Review the instructions the agent will receive before you install.
This skill indexes agentmemory's MCP tools. Use the connected server's tool inventory and schemas; a native memory provider may expose a smaller set under different names. Hermes and OpenClaw skills that need the full surface require a separate MCP connection to the running daemon.
Save then recall:
memory_save with content (the insight), concepts (comma-separated keywords), files (comma-separated paths).memory_smart_search with query, limit, and targetLayer: "memory" to retrieve saved knowledge later. Omit targetLayer to also search captured observations. This runs hybrid BM25 plus vector plus graph-expanded search.memory_save, memory_compress_file. Automatic observations use native hooks or POST /agentmemory/observe, not an MCP observation tool.memory_smart_search, memory_recall, memory_file_history, memory_timeline, memory_vision_search.memory_sessions, memory_commits, memory_commit_lookup.memory_lesson_save, memory_lesson_recall, memory_graph_query, memory_relations, memory_patterns, memory_crystallize.memory_slot_create, memory_slot_append, memory_slot_get, memory_slot_list, memory_slot_replace, memory_slot_delete.memory_governance_delete, memory_audit, memory_verify, memory_heal, memory_diagnose.memory_smart_search for open recall, memory_recall when you already have a focused query, memory_sessions for session listings.memory_recall, distinguish matched_count: 0 from
excluded_by_budget > 0. Expand clipped or omitted IDs with
memory_smart_search and expandIds, preserving the same scope filters.Full tool table with parameters and the core-set marking lives in REFERENCE.md, generated from source so it never drifts.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Connect agentmemory to coding agents such as Claude Code and Codex while preserving existing server settings. It guides configuration, host restarts, and checks that memory tools are available and can save and retrieve information.
Explain how agentmemory stores and retrieves coding agents’ memories, including its engine, search methods, memory lifecycle, ports, and web viewer. Useful for understanding the system or planning extensions to its functions.
Set up and troubleshoot a local agentmemory server by checking MCP connections, authentication, ports, and environment settings. Understand which optional memory features require additional configuration, model downloads, or token usage before enabling them.
Understand how agentmemory automatically records tool activity, prompts, and session boundaries through hooks, actions triggered by session events. Use it to check integration setup, investigate missing records, and distinguish capture from optional summaries and context injection.
Guides HTTP integration with the agentmemory server for saving and searching knowledge. It explains authentication, request conventions, and endpoint references, including how to connect systems that do not support MCP, the agent tool connection protocol.
Trace a file, function, or line through Git history to the agent session linked to its commit. It presents recorded commit details, session summaries, and important observations to help explain the change.