Compact Chat

Compacts conversation history into a structured Markdown file with timestamped filename.

1|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/blink-new/claude --skill compact-chat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Compact Chat
Source: https://github.com/blink-new/claude/tree/main/skills/compact-chat
Command: npx skills add https://github.com/blink-new/claude --skill compact-chat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps preserve valuable context from long conversations by saving a structured summary to disk, preventing loss of information and enabling continuity.

Core Features & Use Cases

  • Conversation Compaction: Generates a detailed, structured summary of the chat history.
  • Context Continuity: Allows resuming work on tasks with preserved context across sessions.
  • Use Case: After a lengthy debugging session where many files were discussed and modified, use this Skill to save a compact summary. This summary will include the problem, solutions, files touched, and pending tasks, making it easy to pick up where you left off later.

Quick Start

Use the compact chat skill to save a summary of the current conversation to a file in the project root.

Frequently Asked Questions about Compact Chat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save conversation context from a long chat session to a file?

To save conversation context, you can compact the chat history into a structured Markdown file with a timestamped filename. This preserves the summary, technical concepts, and pending tasks for future reference across sessions.

What is the best way to resume a debugging session after closing the chat window?

The best way to resume work is by loading a previously saved conversation summary. Compacting the chat into a Markdown file captures touched files, errors, and problem-solving steps, ensuring context continuity when picking up later.

Can I generate a project memory block from chat history for future reference?

Yes, you can generate an optional machine-readable project memory block from your chat history. This feature specifically targets long conversations, extracting current work and next steps into a structured Markdown format.

Does saving chat history to Markdown support custom output locations and filenames?

Saving chat history supports a specified output location and automatically generates a timestamped filename. The filename is derived directly from the conversation's primary topic to keep your context summaries organized.

What specific sections are included when compacting conversation history into a summary?

Compacting conversation history creates a summary with sections for technical concepts, files, errors, problem-solving, user messages, pending tasks, current work, and optional next steps to ensure comprehensive context capture.

When should I use a conversation summary instead of keeping the full chat history?

You should use a conversation summary when managing long chats that risk losing information. Compacting the history into a structured Markdown file prevents context loss and enables continuity without retaining the entire transcript.