os-memory-managerlisted

Trigger with "remember this", "update memory", "what should we record from this session", "capture learnings", "write a session log", or when closing a session. Guides agents on managing memory hygiene across sessions, deciding what to write to dated memory logs, what to promote to long-term memory.md, and when to archive.
richfrem/agent-plugins-skills · ★ 6 · AI & Automation · score 74

Install: claude install-skill richfrem/agent-plugins-skills

# Session Memory Manager Manages the three tiers of agent memory in an Agentic OS environment. Prerequisites, dependencies, and trigger examples are in `references/detailed-reference.md` — this skill requires the Agentic OS to be initialized first (`os-init`). ## Memory Tiers | Tier | File | Written By | When Loaded | |------|------|-----------|-------------| | Auto-memory | `MEMORY.md` | Claude automatically | Every session (Anthropic native) | | Long-term facts | `context/memory.md` | You (curated) | @imported in CLAUDE.md | | Session logs | `context/memory/YYYY-MM-DD.md` | Agent at session close | On demand | ## Execution Flow Execute these phases in order. Do not skip phases. Full detail (templates, dedup protocol, size-limit enforcement, survey questions) for each phase is in `references/detailed-reference.md`. ### Phase 0: Intent Emission (Event Bus) Before taking any actions, publish your intent: `python context/kernel.py emit_event --agent os-memory-manager --type intent --action promote_memory` ### Phase 1: Acquire OS State and Lock 1. Update OS state: `active_agent os-memory-manager`, `mode memory-gc`, `memory_gc_due false`. 2. Acquire the lock: `python context/kernel.py acquire_lock memory`. If it fails, abort. 3. Ask the user to confirm session scope: main task/goal, architectural decisions, tricky bugs solved, skills updated, open next steps. ### Phase 2: Write the Dated Session Log Write to `context/memory/YYYY-MM-DD.md` using today's date, per th