skills.rest
Lsogod
LsogodCOMMUNITY
Explore all skills by this author →
GitHub

compaction-viewer

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

Updated Apr 5, 2026
Search Tags:#transcript#debugging#logs#preprocessing#compaction#token-savings#openclaw
One-click install
npx skills add https://github.com/Lsogod/compaction-debugger --skill compaction-viewer
Or copy as Structured Prompt for Agent▼
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.

Related Skills

Explore More Software Engineering Skills→
LsogodLsogod

context-regression-check

Verifies preprocessing, compaction, and recall behavior after changes.

Community
Intermediate
zhuangharrisonzhuangharrison

词元经济幼儿园 · 入学通知书

Evaluate AI agent token efficiency across three tasks and generate savings reports.

Community
Basic
EndUser123EndUser123

context_status

Parse Claude Code compaction logs to quantify token usage and context size trends.

Community
Intermediate
FrogAiFrogAi
1

save-state

Save the current Codex session state to a JSON snapshot in ~/.codex/compact-saves/.

Community
Intermediate