Menu
Load the Nowledge Mem Working Memory briefing at Proma session start, after a break, or when recent context would help the current task.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | Load the Nowledge Mem Working Memory briefing at Proma session start, after a break, or when recent context would help the current task. |
Read Context Bundle for full Proma startup context when available: owner identity, AI Identity, active scope, active rules, and Working Memory. Read Working Memory alone when you only need current priorities.
Proma's lifecycle hook also writes startup context into the workspace CLAUDE.md inside a nowledge-mem:start / nowledge-mem:end block. Treat that block as the automatic startup layer; call MCP or CLI when you need fresh or more specific retrieval during the session.
Session start: beginning a new Proma conversation, returning after a break, or when recent context would help.
During session: user asks about current work, references recent decisions, or says "what was I working on?"
Skip if: already loaded this session, user wants a fresh start, or the task is isolated and trivial.
Primary (MCP, full startup context):
mcp__nowledge-mem__read_context_bundle
Lightweight MCP:
mcp__nowledge-mem__read_working_memory
CLI Context Bundle fallback:
nmem --json context --source-app proma
Working Memory fallback:
nmem wm read
# or with JSON output:
nmem --json wm read
Add --space "<space name>" for space-aware lanes. Multi-agent orchestrators can set NMEM_AGENT_ID="<agent-slug>" before launching Proma. Add NMEM_SPACE only when that whole run should override the identity's default space. Use NMEM_HOST_AGENT_ID only for advanced external aliases.
The briefing includes: active focus areas ranked by activity, flagged priorities, unresolved flags, recent knowledge-base changes, and deep links to specific memories. Use nowledgemem:// links to reference specific memories when relevant.
If MCP tools are unavailable, verify ~/.proma/agent-workspaces/default/mcp.json has the nowledge-mem server configured with key "servers". For CLI fallback, install via pip install nmem-cli or use the Nowledge Mem desktop app.