Skip to content
Back to skills

Mnemos Memory

ASecurity

Use when users or OpenClaw/ClawHub agents need to install, configure, self-bootstrap, troubleshoot, or operate Mnemos for persistent scoped agent memory, or when they mention Mnemos, agent memory, scoped memory, memory MCP tools, or memory automation.

  • 33 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added May 30, 2026
ai-agentssql

Works with

  • claude code
  • cursor
  • cli
  • mcp

Security analysis

A92/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro scans all 3 files and shows the line behind each finding

Scanned May 30, 2026

npx -y skills add dvcrn/openclaw-skills-marketplace --skill mnemos-memory --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mnemos Memory?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Mnemos Memory
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dvcrn-mnemos-memory/badge)](https://www.skillsdirectory.com/skills/dvcrn-mnemos-memory)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: mnemos-memory
description: "Use when users or OpenClaw/ClawHub agents need to install, configure, self-bootstrap, troubleshoot, or operate Mnemos for persistent scoped agent memory, or when they mention Mnemos, agent memory, scoped memory, memory MCP tools, or memory automation."
---

# Mnemos Memory

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.

## 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 starter store unless the user already has a scale reason for Qdrant or Neo4j.
- 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.
- Neo4jStore is experimental. Do not present it as graph-native spreading-activation persistence yet.

## Workflow

1. Identify the host: Claude Code, Cursor, Codex, OpenClaw, or generic MCP.
2. If the repo is available locally, read `README.md`, `docs/MCP_INTEGRATION.md`, and `docs/codex.md` before answering.
3. Give the default install path first. Only fall back to manual config snippets if the user cannot use the control plane.
4. 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
5. Read `references/hosts.md` for host-specific config snippets and caveats, especially the OpenClaw / ClawHub self-install flow when the agent must bootstrap itself.
6. 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 upgrade users to Qdrant or Neo4j unless they actually need a non-SQLite profile.

Files in this skill

  • SKILL.md2.6 KB
  • references/hosts.md2 KB
  • references/operations.md1.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.