compaction-viewer

Name: compaction-viewer
Availability: InStock
Author: lsogod

Analyze compaction-debugger logs to validate context preprocessing and compression.

Updated Apr 5, 2026

Search Tags:#transcript #debugging #logs #preprocessing #compaction #token-savings #openclaw

Ready to run

npx skills add https://github.com/Lsogod/compaction-debugger --skill compaction-viewer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: compaction-viewer
Source: https://github.com/Lsogod/compaction-debugger/tree/main/skills/compaction-viewer
Command: npx skills add https://github.com/Lsogod/compaction-debugger --skill compaction-viewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps operators verify and understand how the compaction-debugger plugin preprocesses context and what remains after compression, enabling targeted debugging of token savings and recent-message retention.

Core Features & Use Cases

Read and parse the latest assemble-, before-compaction-, and after-compaction logs from the local log directory.
Compare pre- and post-compaction transcripts to identify what was condensed and what was preserved.
Provide quick diagnostics on whether pre-processing was applied and how it affected the current session.

Quick Start

List the latest logs and summarize the pre-processing and compaction results for the current session.

Frequently Asked Questions about compaction-viewer

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

FAQPage Schema

How do I inspect compaction logs to verify token savings?▼

Inspect compaction logs by reading assemble, before-compaction, and after-compaction JSON files to compare pre- and post-compression transcripts, validating token savings and recent-message retention for your session.

What is context preprocessing and how does it affect compaction debugging?▼

Context preprocessing in compaction debugging is the mechanism that condenses transcript data before compression, and analyzing before-compaction logs reveals exactly what was preserved or removed to affect overall token savings.

How do I check what transcript messages are retained after context compression?▼

Check retained transcript messages by comparing before-compaction and after-compaction JSON log files, which provide evidence-based diagnostics on what data was condensed and what was preserved across sessions.

Does the compaction viewer work without external dependencies or plugins?▼

Yes, the compaction viewer works without external dependencies, relying solely on reading local log directory files like assemble-*.json to provide diagnostics on preprocessing and token savings.

What is the best way to debug recent-message retention across sessions?▼

The best way to debug recent-message retention is to parse the latest after-compaction logs from your local directory, summarizing preprocessing results to assess what transcript data remains after compression.