Skill

mnemos-memory

Guides installation, configuration, self-bootstrapping, troubleshooting, and operation of Mnemos for persistent scoped agent memory in Claude Code, OpenClaw, Cursor, Codex, and MCP hosts.

Python

SQLite

npx claudepluginhub anthony-maio/mnemos --plugin mnemos-memory

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Mnemos is a local-first memory layer for coding agents. Use this skill to guide users or OpenClaw agents onto the supported install path, explain the operating loop, and keep compatibility claims accurate.

Supporting Assets

references/hosts.mdreferences/operations.md

SKILL.md

Similar Skills

mnemos-codex

Guides Codex users and agents on installing, configuring, validating, troubleshooting, and operating Mnemos via MCP with recall, curation, and consolidation workflows using mnemos_retrieve, mnemos_store, and related tools.

2 files

mnemos-memory

mnemos

587

Manages task-scoped memory lifecycle in Claude Code using typed MnemoGraph with per-node eviction policies and fatigue monitoring to prevent lossy context compaction. Use for durable checkpoints and handoffs across compactions.

alinaqi-claude-bootstrap

memory-lancedb-pro-openclaw

Guides setup, configuration, and usage of memory-lancedb-pro, LanceDB-backed long-term memory plugin for OpenClaw agents with hybrid retrieval, cross-encoder reranking, and multi-scope isolation.

aradotso-trending-skills-37

Stats

Stars13

Forks1

Last CommitMar 31, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Mnemos Memory

Default path

Prefer pip install "mnemos-memory[mcp]" and mnemos ui.
For OpenClaw / ClawHub, teach the agent to self-install mnemos-memory[mcp], run mnemos ui, then wire mnemos-mcp to the canonical MNEMOS_CONFIG_PATH before relying on memory.
Recommend SQLite as the supported persistent store.
Recommend a real embedding provider (openclaw, openai, openrouter, or ollama) for production retrieval quality.
Validate setup with the control-plane smoke check or mnemos-cli doctor.

Claim discipline

Safe to claim: local-first scoped memory, MCP tools, SQLite starter profile, Claude Code plugin flow, documented Codex flow.
Be explicit that deterministic auto-memory is shipped for Claude Code via hooks.
For Codex, Cursor, OpenClaw, and generic MCP hosts, do not imply automatic capture unless the host has its own automation or the user adds one.
Do not present removed legacy backends as available runtime options.

Workflow

Identify the host: Claude Code, Cursor, Codex, OpenClaw, or generic MCP.
If the repo is available locally, read README.md, docs/MCP_INTEGRATION.md, and docs/codex.md before answering.
Give the default install path first. Only fall back to manual config snippets if the user cannot use the control plane.
Explain the operating loop:
- mnemos_retrieve at task start
- mnemos_store for durable facts only
- mnemos_consolidate before finishing substantial work
- mnemos_inspect when a stored fact looks wrong
Read references/hosts.md for host-specific config snippets and caveats, especially the OpenClaw / ClawHub self-install flow when the agent must bootstrap itself.
Read references/operations.md for automation, capture-mode, storage guidance, and troubleshooting.

Avoid

Do not tell users to manually type memories as the primary workflow.
Do not recommend SimpleEmbeddingProvider for production retrieval quality.
Do not suggest external storage backends for Mnemos. Keep users on the SQLite path.