Skip to content
Back to skills

Save Thread

ASecurity

Create a structured handoff summary when the user asks for a checkpoint. OMP transcript sync is automatic; this skill adds a concise continuation record.

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

Works with

  • api

Security analysis

A100/100

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-ce07cccd/badge)](https://www.skillsdirectory.com/skills/nowledge-co-save-thread-ce07cccd)

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: "Create a structured handoff summary when the user asks for a checkpoint. OMP transcript sync is automatic; this skill adds a concise continuation record."
---

# Save Thread

The Nowledge Mem OMP plugin automatically syncs completed OMP conversations as searchable threads. This skill creates a structured handoff summary when the user wants a concise checkpoint for a future session.

## When to Use

- User asks to save the session: "save this", "checkpoint", "record what we did"
- Session ending with important context that should carry forward
- Complex multi-step work that a future session will resume

Do not use this as routine transcript sync. Use it only when a curated handoff would help a future session resume quickly.

## Usage

```bash
nmem --json t create \
  -t "Session Handoff - <topic>" \
  -c "Goal: ... Decisions: ... Files: ... Risks: ... Next: ..." \
  -s generic-agent
```

## Content Format

Structure the content as a clear handoff. Include only what a future session needs to continue:

```
Goal: What the session set out to accomplish
Decisions: Key choices made and their rationale
Files: Important files created or modified
Outcome: What was achieved
Risks: Known risks, open questions, or things that could break
Next: Concrete steps for the next session
```

### Example

```bash
nmem --json t create \
  -t "Session Handoff - Auth Migration to OAuth2" \
  -c "Goal: Migrate session auth from JWT to OAuth2 with PKCE.
Decisions: Chose Authorization Code flow with PKCE over Implicit for security. Using passport-oauth2 library.
Files: src/auth/oauth2.ts (new), src/auth/middleware.ts (updated), tests/auth.test.ts (updated).
Outcome: Core flow working, token refresh implemented, tests passing.
Risks: Token refresh not tested under clock skew; CSRF state parameter still missing.
Next: Add CSRF state parameter, update API docs, deploy to staging." \
  -s generic-agent
```

## Thread vs Memory

A thread preserves session structure: goals, sequence, context. A memory distills a single insight or decision. They serve different purposes. Use both when appropriate: save the thread for continuity, distill key decisions as standalone memories.

## Links

- [Documentation](https://mem.nowledge.co/docs/integrations/omp)
- [Troubleshooting](https://mem.nowledge.co/docs/troubleshooting)

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.