Skip to content
Back to skills

Save Thread

ASecurity

Save the real Claude Code or Grok Build session messages only when the user explicitly requests it. Use nmem t save to import the recorded session, not a summary-only checkpoint.

  • 182 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
ai-agentsbashapi

Works with

  • claude code
  • cli
  • api

Security analysis

A92/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned September 24, 2026

npx -y skills add nowledge-co/community --skill save-thread --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Save Thread?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Save Thread
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nowledge-co-save-thread-community/badge)](https://www.skillsdirectory.com/skills/nowledge-co-save-thread-community)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: save-thread
description: Save the real Claude Code or Grok Build session messages only when the user explicitly requests it. Use nmem t save to import the recorded session, not a summary-only checkpoint.
---

# 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:

```bash
# 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/project
```

**Options:**
- `--from`: Source app (`claude-code` for Claude Code, `grok` for Grok Build)
- `-s, --summary`: Optional brief summary (recommended)
- `-m, --mode`: `current` (default, latest session) or `all` (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}` or `grok-{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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.