**Type:** Practice / Framework **Dependencies:** None (markdown only) ---
Scanned 2/12/2026
Install via CLI
openskills install openclaw/skills# Agent Memory Kit
**Type:** Practice / Framework
**Dependencies:** None (markdown only)
---
## Description
A structured memory system for AI agents. Prevents the "forgot how to do things" problem by separating memory into episodic (what happened), semantic (what I know), and procedural (how to do things) layers.
## Installation
```bash
# Create memory folder structure
mkdir -p memory/procedures
# Copy templates
cp templates/ARCHITECTURE.md memory/
cp templates/feedback.md memory/
cp templates/procedure-template.md memory/procedures/
```
## Usage
1. Read `README.md` to understand the system
2. Add memory loading to your wake routine (AGENTS.md)
3. Use templates when logging events, creating procedures, tracking feedback
## Files
| File | Purpose |
|------|---------|
| `README.md` | Full documentation |
| `templates/ARCHITECTURE.md` | Memory system overview (copy to memory/) |
| `templates/feedback.md` | Success/failure tracking template |
| `templates/procedure-template.md` | How-to document template |
| `templates/daily-template.md` | Daily log template |
| `templates/compaction-survival.md` | **NEW:** Pre-compaction flush guide |
| `templates/context-snapshot-template.md` | **NEW:** Quick context save template |
| `helpers/check-compaction.sh` | **NEW:** Token limit checker |
## Key Concepts
- **Episodic memory:** Daily logs of WHAT happened
- **Semantic memory:** Curated knowledge (MEMORY.md)
- **Procedural memory:** HOW to do things
- **Feedback loops:** Learn from success/failure
## The Rule
Always capture the **HOW**, not just the WHAT. Future-you needs the steps.
No comments yet. Be the first to comment!
Create Mermaid diagrams for flowcharts, sequences, ERDs, and
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.
Generate the stable Paperclip release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.