القائمة
Read your daily Working Memory briefing to understand current context. Load it near session start for cross-tool continuity, then reuse that context instead of re-reading it repeatedly.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use Nowledge Mem from WorkBuddy or CodeBuddy for startup context, memory search, durable saves, thread search, and WorkBuddy/CodeBuddy transcript import.
Read your daily Working Memory briefing to understand current context. Contains active focus areas, priorities, unresolved flags, and recent knowledge changes. Load this automatically at the beginning of sessions for cross-tool continuity.
Search memory store when past insights would improve response. Recognize when user's stored breakthroughs, decisions, or solutions are relevant. Search proactively based on context, not just explicit requests.
Use Nowledge Mem from Kimi Code for startup context, memory search, durable saves, thread search, and Kimi Code transcript import.
Check Nowledge Mem setup, detect your agent, and guide native connector setup. Use when the user asks about setup, configuration, or when memory tools aren't working as expected.
Save decisions, insights, preferences, and procedures as durable memories. Fires when the conversation produces knowledge worth keeping across sessions.
| name | read-working-memory |
| description | Read your daily Working Memory briefing to understand current context. Load it near session start for cross-tool continuity, then reuse that context instead of re-reading it repeatedly. |
Start each Droid session with context. Use Context Bundle when identity, agent lane, scope, or Rules could matter; it includes Working Memory. Use Working Memory alone for the lighter daily briefing.
Use this near session start, resume, clear, or when the user asks about recent priorities.
Skip when:
Prefer Context Bundle for full startup context:
nmem --json context --source-app droid
Read Working Memory alone for current priorities:
nmem wm read
If the runtime already knows the current project or agent lane, either add --space "<space name>" or launch the whole session with NMEM_SPACE="<space name>". Multi-agent orchestrators can set NMEM_AGENT_ID="<agent-slug>" before launching Droid so the Context Bundle resolves the right AI Identity. Use NMEM_HOST_AGENT_ID only for advanced external aliases.
Fallback for older local-only setups:
cat ~/ai-now/memory.md
This fallback is only for older local-only Default-space setups.
search-memory after the briefing instead of stopping there