// Save or archive the current Proma session to Nowledge Mem when the user explicitly asks, especially as a fallback when automatic hooks are unavailable.
Save durable Nowledge Mem insights when a Proma conversation produces decisions, procedures, preferences, plans, learnings, or project context that should survive future sessions.
Load the Nowledge Mem Working Memory briefing at Proma session start, after a break, or when recent context would help the current task.
Search Nowledge Mem memories and threads from Proma when the user references past work, prior decisions, recurring problems, or project history.
Check whether Nowledge Mem is reachable from Proma, including MCP status, CLI fallback, API URL, and configuration issues after install or update.
Search past decisions, procedures, learnings, or context relevant to the current task. Trigger when work connects to prior decisions, a debugging pattern resembles a past issue, the user asks about rationale, or uses recall language like "that approach" or "like before".
Check Nowledge Mem setup, detect your agent, and guide native plugin installation. Use when the user asks about setup, configuration, or when memory tools aren't working as expected.
| name | save-thread |
| description | Save or archive the current Proma session to Nowledge Mem when the user explicitly asks, especially as a fallback when automatic hooks are unavailable. |
Save the current Proma session to Nowledge Mem on explicit user request.
Save only when the user explicitly requests it:
The Stop hook in ~/.proma/settings.json handles automatic capture after every response. This skill is for manual saves and for fallback when hooks are not configured.
Primary (MCP):
mcp__nowledge-mem__save_thread
session_id: "<current session id>"
title: "<optional custom title>"
Manual script (if MCP unavailable):
echo '{"session_id":"<id>","cwd":"<project dir>"}' | python ~/.proma/hooks/save-to-nmem.py
CLI import (for Proma sessions already on disk):
nmem t save --from proma --project /path/to/project
~/.proma/agent-sessions/<id>.jsonlproma-{session_id}Thread = real session messages (for searching conversation history) Memory = distilled insights (for durable knowledge) Both are useful — save a thread AND distill key learnings.
If thread save fails, check ~/.proma/log/nmem-hook.log for errors. Verify the nmem server is running with nmem status.