Skill

save-topic

Saves structured markdown summaries of current, specific, or all coding topics to persistent files via bash/node scripts. Use to checkpoint progress or persist session state before ending.

Bash

Node

Markdown

developer-tools

automation

npx claudepluginhub hatawong/claude-recap --plugin claude-recap

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Saves a structured summary of a topic to a persistent file. Supports saving the current topic, a specific topic by slug, or multiple topics at once.

SKILL.md

Similar Skills

Session Saver

Generates and saves Markdown session logs capturing objectives, file changes, referenced materials, technical notes, future plans, open items, and metrics to resume project work across conversations.

session-saver

save-conversation

Saves structured summaries of conversations to dated markdown files in conv-logs/ using git project root, checks prior saves to append new topics, tracks skills used, branch, and changed files.

toby-essentials

remember

Saves current work session to persistent memory by summarizing accomplishments, tracking modified files via activity log, and storing learnings for cross-session continuity. Invoke with /remember.

claude-turbo-search

Stats

Stars25

Forks2

Last CommitMar 5, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

save-topic

Overview

Saves a structured summary of a topic to a persistent file. Supports saving the current topic, a specific topic by slug, or multiple topics at once.

Instructions

Preparation

Get the session ID from the SessionStart injection in your context: [SessionStart] session=SESSION_ID source=...
Get the plugin scripts path from the SessionStart injection: Plugin scripts path: /path/to/scripts
Determine which topics to save:
- "save topic" / "checkpoint" → current topic only
- "save topic X" → the specified topic slug
- "save all topics" → all topics in this session

Saving the current topic

Get the current topic slug from your topic tag (the › \slug`` you've been outputting).
Write a structured summary using the format below (section headings in English, content in user's language, skip empty sections):

## Status
What was done, key progress.

## Decisions
What was chosen, why, what was rejected.

## Failures
What was tried, why it failed, the fix or workaround.

## Next Steps
What to do next. Be specific and actionable.

Run:

bash "<plugin_scripts_path>/save-topic.sh" "<slug>" "<session_id>" "<summary>"

Saving a non-current topic

For topics you are NOT currently discussing, your LLM context is likely incomplete. Use the --cold flag to force cold-read from JSONL:

bash "<plugin_scripts_path>/save-topic.sh" --cold "<slug>" "<session_id>" ""

The script will extract the conversation from JSONL and generate a summary via claude -p. The third argument (summary) is ignored when --cold succeeds.

Saving multiple topics

Get all topic slugs by running extract-topic.js (same as list-topics skill step 4): node "<plugin_scripts_path>/extract-topic.js" "$HOME/.claude/projects/<project_id>/<session_id>.jsonl" __all__ Filter out __untagged__ from the output.
Save the current topic using the normal path (LLM writes summary).
Save each non-current topic using the --cold flag.

Rules

State facts only. No AI filler language.
If an existing file for this slug exists, it will be overwritten with the new summary.
This does NOT change the current topic — you continue with the same topic tag after saving.
The summary should cover the entire topic from the start, not just recent progress.
Do NOT copy or build upon any previous summary in your context. Write from scratch based on your full context each time.
For non-current topics, always use --cold — do not attempt to write summaries from degraded LLM memory.