Save Thread
- 669 installs
- 148 repo stars
- Updated August 3, 2026
- nowledge-co/community
save-thread is an agent skill that imports full Claude Code or Grok Build session messages into nmem for developers who need an explicit, resumable conversation checkpoint instead of a summary-only handoff.
About
save-thread is a nowledge-co/community skill that records real agent session messages only when a developer explicitly requests a checkpoint. It uses the nmem CLI command nmem t save with --from claude-code or --from grok to import the current session for the active project, optionally attaching a brief custom summary via -s. The skill forbids auto-save or unsolicited suggestions, keeping thread archives intentional and clean. Developers reach for save-thread before context limits, team handoffs, or pausing multi-step agent work that must resume with full message history. It complements summary checkpoints by preserving the underlying conversation, not a distilled recap alone.
- Deprecated compatibility alias for save-handoff
- Degrades gracefully in generic npx skills environments
- Creates concise resumable handoff using nmem t create
- Clearly labels output as handoff summary rather than full transcript
- Prevents false expectations about lossless thread import
Save Thread by the numbers
- 669 all-time installs (skills.sh)
- +17 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #1,451 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/nowledge-co/community --skill save-threadAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 669 |
|---|---|
| repo stars | ★ 148 |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 3, 2026 |
| Repository | nowledge-co/community ↗ |
How do you checkpoint a full agent session?
Maintain a clean, resumable handoff when an agent conversation needs to be preserved or continued later.
Who is it for?
Developers using Claude Code or Grok Build who explicitly want full session history preserved in nmem for handoff or later continuation.
Skip if: Developers who only need lightweight auto-checkpoints or summary-only context without importing raw session messages.
When should I use this skill?
The user explicitly says save this session, checkpoint this, or record conversation and wants nmem thread import.
What you get
An nmem project thread containing imported session messages and an optional brief summary for later resumption.
- nmem thread with imported session messages
Files
Save Thread
When to Save
Only when user explicitly says: "Save this session" | "Checkpoint this" | "Record conversation"
Never auto-save or suggest.
Tool Usage
Use nmem t save to import the current session. Use claude-code in Claude Code and grok in Grok Build:
# Save current session for current project
nmem t save --from claude-code
# In Grok Build:
nmem t save --from grok
# Save with custom summary
nmem t save --from claude-code -s "Brief summary of what was accomplished"
# In Grok Build:
nmem t save --from grok -s "Brief summary of what was accomplished"
# Save all sessions for current project
nmem t save --from claude-code -m all
# In Grok Build:
nmem t save --from grok -m all
# Save for specific project path
nmem t save --from claude-code -p /path/to/project
# In Grok Build:
nmem t save --from grok -p /path/to/projectOptions:
--from: Source app (claude-codefor Claude Code,grokfor Grok Build)-s, --summary: Optional brief summary (recommended)-m, --mode:current(default, latest session) orall(all sessions)-p, --project: Project directory path (defaults to current directory)--truncate: Truncate large tool results (>10KB)
Behavior:
- Auto-detects sessions from
~/.claude/projects/for Claude Code or~/.grok/sessions/for Grok Build - Idempotent: Re-running appends only new messages
- Thread ID: Auto-generated as
claude-code-{session_id}orgrok-{session_id}
Thread vs Memory
Thread = real session messages | Memory = distilled insights (different purposes, can do both)
Response
✓ Thread saved
Summary: {summary}
Messages: {count}
Thread ID: claude-code-{session_id} or grok-{session_id}Troubleshooting
If nmem is not in PATH: pip install nmem-cli, or on Arch Linux yay -S nmem-cli / paru -S nmem-cli
For remote servers: run nmem config client set url https://... and nmem config client set api-key ... once on this machine.
Run /status to check server connection.
Related skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10FAQ
What command does save-thread use?
save-thread runs nmem t save with --from claude-code in Claude Code or --from grok in Grok Build, optionally adding -s for a brief summary while importing full session messages.
Does save-thread auto-save agent sessions?
save-thread never auto-saves or suggests saving. The skill runs only when a developer explicitly requests phrases like save this session, checkpoint this, or record conversation.
Is Save Thread safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.