Save Thread

nowledge-co/community/nowledge-mem-proma-plugin/skills/save-thread

by nowledge-co1f4d7eb61466dbfc93ce8d7a0a806c4d4a196dd0No licenseListed Oct 9, 2026Updated Oct 9, 2026

Save or archive the current Proma session to Nowledge Mem when the user explicitly asks, especially as a fallback when automatic hooks are unavailable.

Instructions onlyProductivity & Workflow

AI-generated overview

Saves or archives the current Proma session to Nowledge Mem on explicit user request, as a manual fallback to automatic hooks.

What it does: This skill instructs an agent to save the current Proma session to Nowledge Mem only when the user explicitly asks, such as "Save this session" or "Archive this conversation". It describes using the MCP tool mcpnowledge-memsave_thread with a session id and optional title, or a manual Python script fallback if MCP is unavailable. It notes that saves are deduplicated by UUID, idempotent, and that threads can be complemented by distilled memories.
When to use it: Use it when a user explicitly asks to save, archive, record, or checkpoint the current session. It is also intended as a fallback when the automatic UserPromptSubmit and Stop hooks are not configured. It is not for automatic capture, which the hooks handle.
Requirements: Requires the Nowledge Mem MCP tool mcpnowledge-memsave_thread, or alternatively a Python 3 script at ~/.proma/scripts/save-to-nmem.py. It also references Proma session JSONL files under ~/.proma/sdk-config/projects/ or ~/.proma/agent-sessions/, a running nmem server, and a log at ~/.proma/logs/nm-hooks.log. The skill ships no scripts of its own.

Save Thread

Save the current Proma session to Nowledge Mem on explicit user request.

When to Save

Save only when the user explicitly requests it:

"Save this session"
"Archive this conversation"
"Record this"
"Checkpoint this"

The UserPromptSubmit and Stop hooks in ~/.proma/sdk-config/.claude/settings.json handle automatic capture. This skill is for manual saves and for fallback when hooks are not configured.

Usage

Primary (MCP):

mcp__nowledge-mem__save_thread  session_id: "<current session id>"  title: "<optional custom title>"

mcp__nowledge-mem__save_thread  session_id: "<current session id>"  title: "<optional custom title>"

Manual script (if MCP unavailable):

Behavior

Proma sessions are stored as JSONL in ~/.proma/sdk-config/projects/<workspace-hash>/<session-id>.jsonl
Older Proma builds that write ~/.proma/agent-sessions/<id>.jsonl are still supported by the script
The save script deduplicates by UUID and extracts text from content blocks
Thread ID format: proma-{session_id}
Re-running is idempotent — only new messages are appended

Thread vs Memory

Thread = real session messages (for searching conversation history) Memory = distilled insights (for durable knowledge) Both are useful — save a thread AND distill key learnings.

Troubleshooting

If thread save fails, check ~/.proma/logs/nm-hooks.log for errors. Verify the nmem server is running with nmem status.

Source and attribution

Source:nowledge-co/communityinnowledge-mem-proma-plugin/skills/save-threadat commit1f4d7eb

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Save Thread

Save Thread

When to Save

Usage

Behavior

Thread vs Memory

Troubleshooting

Source and attribution

More from nowledge-co/community

Read Working Memory

Search Memory

Save Thread

Distill Memory

Search Memory

Read Working Memory

More in Productivity & Workflow

Morning Note

Dd Meeting Prep

Dd Checklist

Deal Tracker

Client Review

Morning Note