القائمة
Save the real Gemini CLI session to Nowledge Mem only when the user explicitly asks. This uses Gemini's native transcript-backed importer rather than a summary-only fallback.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Read the user's daily Working Memory briefing at session start or when recent priorities matter. This gives Gemini CLI cross-tool continuity without bloating the main prompt.
Detect breakthrough moments, durable lessons, and decisions worth preserving. Suggest distillation sparingly, then store high-value knowledge as atomic memories.
Search the user's personal knowledge base when past insights would improve the response. Trigger proactively for continuity, recurring bugs, design rationale, and remembered workflows.
Save a concise Gemini CLI handoff summary only when the user explicitly asks. This is intentionally separate from full thread-save, which should use the native Gemini session importer.
| name | save-thread |
| description | Save the real Gemini CLI session to Nowledge Mem only when the user explicitly asks. This uses Gemini's native transcript-backed importer rather than a summary-only fallback. |
Only use this skill when the user explicitly asks to save the session, persist the thread, or store the actual Gemini conversation.
save-thread means saving the real Gemini session messages.
Use nmem t save --from gemini-cli for that path. A short summary may be attached as metadata, but the stored thread should come from Gemini's recorded transcript.
Use save-handoff instead only when the user wants a lightweight resumable summary rather than the full session.
nmem --json t save --from gemini-cli -p . -s "...".--session-id.Example:
nmem --json t save --from gemini-cli -p . -s "Finished the auth refactor and verified the new refresh-token flow."
Never claim a checkpoint summary is a thread save. Never auto-save without an explicit user request.