memory

Store and recall durable facts and decisions using the Mnemosyne CLI.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/wesbragagt/nixos-config --skill memory-wesbragagt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory
Source: https://github.com/wesbragagt/nixos-config/tree/main/home/skills/memory
Command: npx skills add https://github.com/wesbragagt/nixos-config --skill memory-wesbragagt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Important decisions, debugging discoveries, and user corrections are lost between sessions, forcing repeated investigation of the same problems. This Skill persists durable facts to a local memory bank and recalls them before non-trivial work begins. ## Core Features & Use Cases - Store confirmed facts: Record decisions, host-specific quirks, conventions, and user corrections with a source label via mnemosyne store. - Recall before work: Query relevant memory with mnemosyne recall before recurring or non-trivial tasks to avoid repeated debugging. - Manage memory lifecycle: List, update, and delete stale entries with mnemosyne stats, update, and delete. - Use Case: After debugging a NixOS host quirk, store the finding; weeks later, recall it before touching that host again instead of rediscovering the issue. ## Quick Start Ask the assistant to remember a confirmed fact or recall what is known about a topic using the Mnemosyne memory skill.

Frequently Asked Questions about memory

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

FAQPage Schema
How do I store a memory with the Mnemosyne CLI?

Run mnemosyne store with the fact and a short source label such as session, user-correction, or debugging. Set MNEMOSYNE_DATA_DIR and MNEMOSYNE_BANK environment variables first so the command targets the correct data directory and bank.

How do I recall previously stored memories?

Run mnemosyne recall with a topic string to retrieve relevant stored memories. Recalled memory is background context only; current user instructions and actual repository state take precedence over stale entries.

Why does passing --bank to mnemosyne store fail?

The --bank flag exists only on mnemosyne mcp. Data commands like store, recall, and stats read the bank from the MNEMOSYNE_BANK environment variable, so --bank is parsed as a positional argument and fails.

When should I store a memory versus skip it?

Store a fact only after it is confirmed true: decisions with reasons, host-specific quirks found through debugging, non-obvious conventions, or user corrections. Do not store speculative or unverified information.

Can I use separate memory banks for different projects?

The default bank is shared across projects by design. Use a separate data directory and bank only when the user explicitly requests isolated memory for a specific context.