ce-session-extract

Extract narrative skeletons or error signals from session JSONL files.

2|Updated May 8, 2026
One-click install
npx skills add https://github.com/xotong/claude-marketplace --skill ce-session-extract-xotong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-session-extract
Source: https://github.com/xotong/claude-marketplace/tree/main/plugins/compound-engineering/skills/ce-session-extract
Command: npx skills add https://github.com/xotong/claude-marketplace --skill ce-session-extract-xotong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill extracts filtered content from a single Claude Code, Codex, or Cursor session file — producing either a narrative skeleton or error signals to keep context lean.

Core Features & Use Cases

  • Skeleton extraction: generates a compact narrative of user and assistant turns with collapsed tool calls to minimize context size.
  • Error signal extraction: surfaces failed tool results and error messages with timestamps for quick triage.
  • Platform versatility: supports Claude Code, Codex, and Cursor transcripts for unified analysis.
  • Deteministic output: emits a structured _meta summary containing line counts and parse results for reliability.

Quick Start

Pipe a single session JSONL file to the skill to receive a readable skeleton or error digest.

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 error signals from a Claude Code session JSONL file?

To extract error signals from a Claude Code session JSONL file, pipe the file into the skill to surface failed tool results and error messages with timestamps. It outputs a deterministic, parse-friendly digest for quick triage.

Can I extract a narrative skeleton from Codex or Cursor session logs?

You can extract a narrative skeleton from Codex or Cursor session logs by piping the JSONL file into the skill. It generates a compact narrative of user and assistant turns with collapsed tool calls to minimize context size.

What is the best way to reduce context size when analyzing session JSONL transcripts?

The best way to reduce context size when analyzing session JSONL transcripts is to extract a filtered skeleton or error signals. This collapses tool calls and removes unnecessary content, producing a lean digest with a final _meta summary.

Does session skeleton extraction work across different AI coding platforms?

Session skeleton extraction works across Claude Code, Codex, and Cursor platforms for unified analysis. It supports parsing transcripts from these environments to keep context within limits during analysis.

How do I parse a single session JSONL file to get a structured summary?

To parse a single session JSONL file for a structured summary, pipe the file to the skill to receive a readable skeleton or error digest. The output includes a deterministic _meta summary containing line counts and parse results.