Use when the user asks to "remember project context", review saved findings, initialize runtime memory, archive stale work, reconcile notes, or erase a subject; manages authorized HOT/WARM/COLD working memory across all disciplines while preserving registry event ownership and privacy controls. Not for changing canonical registry facts - route those through the owning registry. 项目记忆/跨会话
SkillScore88Maintained
Automatic
◆Knowledge Management pack
Last verified 8/27/2026
What it changes
Passed 21 of 24 test cases with the skill, and 8 of 24 without it.
Without skill33%
With skill88%
Checks it passed that the model alone missed
The response specifies using the /show-memory command.
The response specifies using the /export-memory command.
The JSON envelope includes source and confidence metadata properties.
and 13 more in the full report
13 fixed8 passed either way3 still failing0 broke
Pass-rate lift
+54 pp
Tokens
+192%
Agent turns
0%
Response time
-26%
Model gemini-3.6-flashMeasured 8/27/2026v221 of 24 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
The user previously stored an import style preference, but now wants to wipe that specific preference completely without erasing architectural decisions or tech stack knowledge. Provide the command to invoke.
What was checked, without and with the skill
Checked
Without skill
With skill
The response specifies using the /clear-memory command with the target topic name.
Missed
Passed
case-11 · gemini-3.6-flash · 8/27/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md591 linessingle file
Memory Management Skill
Purpose
Guide Claude Code to intentionally capture, store, and use context, decisions, and preferences across sessions, enabling true "memory" that survives context resets and improves over time.
When to Use This Skill
Automatically activates when you mention:
Remembering user preferences or choices
Tracking decisions made during development
Capturing important context
Learning from user corrections
Persisting project-specific knowledge
Memory that survives session resets
The Problem: Context Loss
Without intentional memory:
❌ Same mistakes repeated across sessions
❌ User has to re-explain preferences every time
❌ Important decisions forgotten after context reset
❌ No learning from corrections
❌ Starting from scratch each session
With intentional memory:
✅ Preferences remembered and auto-applied
✅ Decisions documented and retrievable
✅ Context persists across sessions
✅ Learn and adapt from corrections
✅ Continuous improvement over time
Core Principles
1. Be Selective
Track signal, not noise:
✅ User explicitly states preference ("always use X")