memory-set

Solid

Maintain prompt-facing working memory by editing MEMORY.md when GUIDE.md indicates that durable information should be kept.

AI & Automation 322 stars 46 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 90/100

Stars 20%
84
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# memory-set Use this skill only after the HostAgent has decided, according to `GUIDE.md`, that working memory should be updated. ## Boundary This skill edits `MEMORY.md`. It does not write Mnemon long-term memory. Long- term consolidation belongs to the dreaming subagent. Resolve the working memory path as: ```text $MNEMON_MEMORY_LOOP_DIR/MEMORY.md ``` If `MNEMON_MEMORY_LOOP_DIR` is not available, use the path injected by the Prime hook. Do not guess a repository-root `MEMORY.md`, `~/.mnemon/MEMORY.md`, or a runtime-specific default unless the HostAgent has explicitly provided that path. ## Procedure 1. Identify the smallest durable memory worth keeping. 2. Open `$MNEMON_MEMORY_LOOP_DIR/MEMORY.md`. 3. Preserve any organization already present in `MEMORY.md`. If the file has no useful structure yet, create the smallest heading or bullet layout needed for the current memory. 4. Apply a minimal edit: - add a concise bullet; - replace stale or superseded wording; - remove obsolete or unsafe content. 5. Prefer one clear sentence over a transcript excerpt. 6. Merge by default: same topic, same preference, or same decision should update the existing entry instead of appending a new one. 7. Defer unstable memories. If the user is still negotiating wording or making a first passing mention, leave `MEMORY.md` unchanged. 8. Keep the file compact. If the file is becoming long or repetitive, trigger or recommend dreaming instead of appending more text. 9. ...

Details

Author
mnemon-dev
Repository
mnemon-dev/mnemon
Created
3 months ago
Last Updated
today
Language
Go
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

memory

Manage durable project memory with MEMORY.md index, topic files, and modular rule packs.

2 Updated today
ibahgat
AI & Automation Solid

memory-get

Recall long-term memory from Mnemon when GUIDE.md indicates that prior memory may help the current task.

322 Updated today
mnemon-dev
Code & Development Solid

memory-cleanup

Use this skill when performing manual memory consolidation (Dream-equivalent). Reviews, consolidates, and prunes memory files under ~/.claude/projects/*/memory/. Run after major refactors, every 5+ sessions, or when memory quality degrades (broken links, stale references, contradictions, MEMORY.md > 200 lines). Invoke with /memory-cleanup.

48 Updated 2 days ago
Kanevry
AI & Automation Featured

memory-kit

Persistent context management for Claude Code sessions. Save, load, update, share, and audit session memory via MEMORY.md. Prevents context loss on compaction or session restart. Use when starting a session, before compaction, syncing context across teammates, or pruning stale memory entries. Trigger with "save memory", "load memory", "memory audit", "memory share".

2,274 Updated today
jeremylongshore
AI & Automation Listed

bettermemory

Verification-grade memory between sessions. Use bettermemory's MCP tools (memory_search, memory_show, memory_write, memory_verify, memory_record_use, etc.) instead of writing to files when the user asks you to "remember" something or references shared context from a past session. Default is to NOT call memory_search; only retrieve when the user references context you don't have ("my project", "the script we wrote") or a request is ambiguous in a way stored preferences could resolve. Every hit carries a staleness_verdict (calendar + path-drift + commit-drift); when it isn't "fresh", spot-check a claim before relying and call memory_verify to attest. Every use should record a claim_excerpt so retrievals stay auditable.

0 Updated today
0Mattias