memory-status
Show the current status of the memory system: file counts, index size, last maintenance time, pending wrapups, etc.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Show the current status of the memory system: file counts, index size, last maintenance time, pending wrapups, etc.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | memory-status |
| description | Show the current status of the memory system: file counts, index size, last maintenance time, pending wrapups, etc. |
| allowed-tools | ["Read","Glob","Bash"] |
Read and report memory system status:
cat "$HOME/.aria-memory/meta.json" 2>/dev/null || echo '{"error": "meta.json not found"}'
find "$HOME/.aria-memory/knowledge" -maxdepth 1 -name "*.md" 2>/dev/null | wc -l
echo "Active: $(find "$HOME/.aria-memory/impressions" -maxdepth 1 -name "*.md" 2>/dev/null | wc -l)"
echo "Archived: $(find "$HOME/.aria-memory/impressions/archived" -maxdepth 1 -name "*.md" 2>/dev/null | wc -l)"
wc -l "$HOME/.aria-memory/index.md" 2>/dev/null
Present a concise status dashboard like:
=== Aria Memory Status ===
Index entries: XX lines
Knowledge files: XX
Impressions: XX active / XX archived
Pending wrapups: XX
Last maintenance: YYYY-MM-DD HH:MM (XX hours ago)
Index version: XX
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.
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.
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.