一键导入
read-working-memory
Read the user's Working Memory briefing when current priorities, recent activity, or active focus areas matter.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Read the user's Working Memory briefing when current priorities, recent activity, or active focus areas matter.
用 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 the user's Working Memory briefing when current priorities, recent activity, or active focus areas matter. |
Use read_context_bundle when startup identity, agent lane, space scope, or Rules could matter. It includes owner identity, resolved AI Identity, active scope, active rules, Working Memory, and KFS paths.
Use the read_working_memory MCP tool to load only the user's current focus, priorities, and unresolved context when the session-start hook did not already provide it or when a lightweight refresh is needed.
<nowledge_working_memory> block is already present, reuse it instead of reading again immediately.search-memory after the briefing instead of stopping there.Summarize only the parts relevant to the current task.