mnemos-memory

Store and retrieve persistent memories across agent sessions via API.

29|7|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/ncz-os/mnemos --skill mnemos-memory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mnemos-memory
Source: https://github.com/ncz-os/mnemos/tree/main/integrations/openclaw/.agents/skills/mnemos-memory
Command: npx skills add https://github.com/ncz-os/mnemos --skill mnemos-memory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MNEMOS Memory provides a persistent memory service accessible across agent sessions. It enables reading and writing memories to capture decisions, context, patterns, and standards, with full-text and semantic search and support for organizing knowledge via category and knowledge-graph triples.

Core Features & Use Cases

  • Persistent memory store across agent sessions
  • Full-text and semantic search
  • Create/update/delete memories with categories (decisions, solutions, patterns, infrastructure, projects, standards)
  • Knowledge graph triples for relational facts
  • Use case: Capture architectural decisions and retrieve them during long-running tasks

Quick Start

Store a memory about a recent decision, then retrieve it later by category using the mnemos memory API.

Frequently Asked Questions about mnemos-memory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist agent context across multiple sessions?

To persist agent context across sessions, you need a memory store that captures decisions and standards. This Skill provides an API to store and retrieve persistent memories using full-text search and knowledge-graph triples.

What is a knowledge graph triple for AI agent memory?

A knowledge graph triple is a relational fact structure used to organize memories. It allows persistent memory services to store relational facts alongside categorized content, enabling agents to retrieve complex project context and architectural decisions.

How do I store architectural decisions for retrieval during long-running tasks?

To store architectural decisions for long-running tasks, use a memory API to save content with a specific category like decisions. You can retrieve these memories later through full-text or semantic search by filtering for that category.

Does agent memory persistence require an external API?

Yes, persistent memory across agent sessions requires an API to store content, categories, subcategories, and metadata. The API must support retrieving these memories through text and category search and managing knowledge-graph triples.

Can I search memories by category and text content?

Yes, you can search memories by category and text content. The persistent memory store supports full-text and semantic search, allowing you to filter memories by categories like solutions, patterns, infrastructure, projects, and standards.

What are the limitations of using knowledge graph triples for agent memory?

Knowledge graph triples for agent memory are limited to storing relational facts. They must be paired with categorized content and metadata to fully capture complex project context, and retrieval depends on available full-text and semantic search capabilities.