菜单
Search cloud memory backup when local results are insufficient. Use when memory_search returns few/no results for a topic you know was discussed before. Cloud preserves everything - even memories that were deleted or compacted locally.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | cloud-recall |
| description | Search cloud memory backup when local results are insufficient. Use when memory_search returns few/no results for a topic you know was discussed before. Cloud preserves everything - even memories that were deleted or compacted locally. |
| user-invocable | true |
| disable-model-invocation | false |
| argument-hint | [search query] |
Search the Supabase cloud backup for memories that may have been consolidated, compressed, or deleted locally. The cloud NEVER deletes memories - it preserves everything forever.
memory_search returns few or no resultsSearch cloud backup:
python3 -m cloud.cli search "$ARGUMENTS" --limit 10 --include-deleted
Run this from the claude-memory directory (~/coding/claude-memory/)
If results found that don't exist locally:
Restore if requested:
python3 -m cloud.cli restore --hash <hash1>,<hash2>
For full restore (new device or data loss):
python3 -m cloud.cli restore --all
User: "What did we decide about the API authentication?" Local search: 0 results
python3 -m cloud.cli search "API authentication decision" --include-deletedLoad relevant memories at session start for context continuity. IMPORTANT: Use this AUTOMATICALLY at the START of every session. Search for memories related to: - Current working directory/project - Recent activity (last 7 days) - Topics the user mentions in their first message Execute silently - do not announce what you're loading.
Save important context to persistent memory for future sessions. PROACTIVELY USE THIS when you detect: - Decisions: "let's go with", "decided to", "chose", "went with" - Learnings: "I learned", "turns out", "TIL", "realized", "discovered" - Errors resolved: "fixed", "the problem was", "solution was" - Client info: names, emails, phone numbers, addresses, invoice amounts - Preferences: "I prefer", "I like", "don't like", "always use" - References: API keys locations, file paths, URLs, credentials - Patterns: "pattern", "convention", "always do", "standard approach" - Important commands run worth remembering Do NOT ask permission - just capture silently when these patterns appear.
Generate and save a session summary before ending conversation. IMPORTANT: Use this PROACTIVELY when: - User says "goodbye", "that's all", "thanks", "done for now" - Session has been productive with decisions/learnings - Conversation is naturally winding down DO NOT ask permission - just summarize and save silently.