菜单
Manually trigger session wrapup to process the current conversation into long-term memory. Use before ending a long or important session to ensure key information is captured. TRIGGER when: user says "save this session", "wrap up memory", or before ending an important conversation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | memory-wrapup |
| description | Manually trigger session wrapup to process the current conversation into long-term memory. Use before ending a long or important session to ensure key information is captured. TRIGGER when: user says "save this session", "wrap up memory", or before ending an important conversation. |
| allowed-tools | ["Agent","Read","Bash"] |
Trigger a manual session wrapup:
ls -t ~/.claude/projects/*/*.jsonl 2>/dev/null | head -5
Select the most recent transcript file that matches the current session.
Pass to memory-agent subagent:
{
"type": "session_wrapup",
"memoryDir": "!`echo $HOME/.aria-memory`",
"transcriptFile": "<path to the most recent transcript>",
"sessionDate": "!`date +%Y-%m-%d`"
}
Report what was captured and stored.
Send a proactive Telegram message by spawning a fresh headless Claude session (not the current one). Use this when the user asks for scheduled or fire-and-forget tasks that end in a Telegram notification — it avoids the 409 Conflict that would occur if a second session tried to load the telegram plugin alongside the current one.
Set up automatic memory maintenance using /loop. Creates a recurring loop that triggers /memory-sleep periodically.
Query the long-term memory system. Use when the user asks about past conversations, previously discussed topics, stored preferences, or project knowledge from earlier sessions. TRIGGER when: user references past conversations, asks "do you remember", wants to recall something discussed before, or needs context from previous sessions.
Trigger global memory maintenance (global_sleep). This performs index compaction, knowledge file splitting, cross-reference maintenance, and cleanup. Only needed periodically or when memory feels cluttered.
Show the current status of the memory system: file counts, index size, last maintenance time, pending wrapups, etc.
Store information in long-term memory. Use when the user explicitly asks to remember something, or when important information is shared that should persist across sessions. TRIGGER when: user says "remember this", "store this", "save this for later", or shares critical project/personal information.