chat_compactor

Condense extensive chat histories into structured summaries within token limits.

7|Updated May 6, 2026
One-click install
npx skills add https://github.com/tya5/reyn --skill chat-compactor-tya5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chat_compactor
Source: https://github.com/tya5/reyn/tree/main/src/reyn/stdlib/skills/chat_compactor
Command: npx skills add https://github.com/tya5/reyn --skill chat-compactor-tya5

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of managing long chat histories by automatically generating concise summaries that fit within token constraints, ensuring smooth, continuous conversations without exceeding context limits.

Core Features & Use Cases

  • Structured Chat Summarization: Creates a rolling summary of chat sessions that includes key decisions, pending items, and user facts.
  • Token Budget Management: Selectively drops low-importance information to stay within per-section token caps.
  • Use Case: When a user’s conversation extends beyond manageable length, generate a compact summary to preserve relevant context and continue interactions seamlessly.

Quick Start

Use the chat_compactor skill to summarize recent chat turns and maintain an efficient context window in an ongoing session.

Frequently Asked Questions about chat_compactor

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

FAQPage Schema
How do I summarize chat history to stay within token limits?

To summarize chat history within token limits, you can automate the condensation of extensive chat turns into structured summaries, selectively dropping low-importance information to preserve key context for ongoing conversations.

What is the best way to manage context size for long chat sessions?

The best way to manage context size for long chat sessions is by applying token budget management, which generates a rolling summary of key decisions and pending items while dropping low-importance information to maintain an efficient context window.

When do I need to condense conversation histories into a rolling summary?

You need to condense conversation histories into a rolling summary when a user's conversation extends beyond manageable length, allowing you to preserve relevant context and continue interactions seamlessly without exceeding token constraints.

Does chat session summarization preserve key user facts and pending items?

Yes, chat session summarization preserves key user facts and pending items by parsing chat turn data and applying retention rules to generate structured summaries that maintain essential context within per-section token caps.

Can I use automated context condensation for long-term chat preservation?

Yes, you can use automated context condensation for long-term chat preservation, as it updates summaries efficiently by parsing chat turn data and applying retention rules to optimize context size over extended sessions.

What are the limitations of token budget management for chat histories?

A limitation of token budget management for chat histories is that it must selectively drop low-importance information to stay within per-section token caps, meaning some granular details from the original chat turns may be lost during the condensation process.