ce-session-extract

Extract conversation skeletons or error signals from session JSONL files.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026 --skill ce-session-extract-diestok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-session-extract
Source: https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026/tree/main/.agents/skills/compound-engineering/skills/ce-session-extract
Command: npx skills add https://github.com/DieStok/ridder_lab_retreat_ai_hackathon_2026 --skill ce-session-extract-diestok

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Large session JSONL files produced by Claude Code, Codex, or Cursor are difficult to analyze directly. This Skill provides a deterministic way to produce concise digests that highlight user/assistant dialogue structure or error signals.

Core Features & Use Cases

  • Extract conversation skeletons: produce a readable sequence of user and assistant messages with collapsed tool calls.
  • Extract errors: surface failed tool calls and error signals for debugging and auditing.
  • Works with single-session files to keep context manageable and enables downstream analysis by agents.

Quick Start

Run ce-session-extract on a session file to generate a compact digest of the chosen mode.

Frequently Asked Questions about ce-session-extract

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

FAQPage Schema
How do I extract conversation skeletons from large JSONL session logs?

Extract conversation skeletons from JSONL session logs by running a Python script pipeline that collapses tool calls and produces a readable digest of user and assistant dialogue sequences.

Can I surface failed tool calls and error signals from Claude Code or Cursor sessions?

Yes, you can surface failed tool calls and error signals from Claude Code or Cursor sessions by extracting error signals from the single-session JSONL file for debugging and auditing purposes.

What is a session skeleton digest and when do I need one for debugging?

A session skeleton digest is a concise, readable summary of user and assistant dialogue with collapsed tool calls from a single JSONL file, needed when analyzing long coding sessions for debugging and research.

Does ce-session-extract work with single-session files or can it batch process multiple logs?

ce-session-extract works with single-session JSONL files to keep context manageable, applying a deterministic pipeline to generate digests rather than batch processing multiple logs at once.

Are there line limits for extracting digests from very long Codex session JSONL files?

Yes, the extraction pipeline supports optional line-limits when processing very long Codex session JSONL files, emitting a final _meta line with line counts and error statistics for tracking.