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

session-memory-inspector

Identify usable Pi memories from assemble and after-compaction JSON files.

Updated Apr 5, 2026
Search Tags:#preprocessing#compaction#session-memory#memory-inspection#assemble-json#after-compaction
One-click install
npx skills add https://github.com/Lsogod/compaction-debugger --skill session-memory-inspector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-memory-inspector
Source: https://github.com/Lsogod/compaction-debugger/tree/main/skills/session-memory-inspector
Command: npx skills add https://github.com/Lsogod/compaction-debugger --skill session-memory-inspector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps users understand which parts of a session remain usable as Pi memories after preprocessing or compaction, enabling quick visibility into what the system can still rely on.

Core Features & Use Cases

  • Memory visibility: identify memories still present in recent messages, those compressed into summaries, and those moved into compaction summaries.
  • Evidence-driven reporting: extract facts, goals, decisions, constraints, and errors from the session's memory state.
  • Audit-ready outputs: clearly separate items that remain explicit from those that exist only in the summary, and flag uncertain items when evidence is insufficient.
  • Use Case: a user checks a session to confirm which earlier facts are still accessible before deciding on a follow-up action.

Quick Start

Inspect the current memory state of a selected session by requesting a report that compares the latest assemble and after-compaction outputs.

Frequently Asked Questions about session-memory-inspector

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

FAQPage Schema
How do I check which session memories are still accessible after compaction?▼

To check session memories after compaction, review the latest assemble-*.json and after-compaction-*.json files to identify which facts, goals, decisions, constraints, and errors remain visible or were compressed into summaries.

What is the difference between explicit memories and summary-only items in a session transcript?▼

Explicit memories remain directly visible in recent session messages, while summary-only items exist solely within compaction summaries, requiring evidence-driven auditing to distinguish their availability and flag uncertain items lacking proof.

How do I audit session memory visibility before taking a follow-up action?▼

Audit session memory visibility by comparing the latest assemble and after-compaction outputs, clearly separating memories that remain explicit from those existing only in summaries, and marking uncertain items when evidence is insufficient.

Can I extract facts and decisions from a compaction summary without reading the full transcript?▼

Yes, you can extract facts, goals, decisions, constraints, and errors directly from the after-compaction-*.json file to determine what the system can still rely on, only reviewing the full transcript if needed for missing evidence.

What are the limitations of inspecting preprocessed session memory?▼

Limitations include the inability to recover memories completely lost during preprocessing, and the necessity to flag uncertain items as assumptions when the compaction summary or transcript lacks sufficient evidence to confirm their visibility.

Related Skills

Explore More Software Engineering Skills→
LsogodLsogod

compaction-viewer

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

Community
Intermediate
AlvaroLaraFFAlvaroLaraFF

memory-consolidate

Audit memory entries for age, vagueness, and data leaks.

Community
Advanced
MilUX-LtdMilUX-Ltd

summarize-interview

Synthesize research interview transcripts into structured summaries with key insights and action items.

Official
Intermediate
arnaudjnnarnaudjnn
1

add-compact

Implement a manual /compact command to summarize and condense conversation history.

Community
Advanced