ce-session-extract

Extract conversation skeletons or error signals from Claude Code, Codex, and Cursor session JSONL files.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-session-extract-norfolk-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-session-extract
Source: https://github.com/Norfolk-Group/marcela-norfolk-ai/tree/main/skills/compound-engineering/skills/ce-session-extract
Command: npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-session-extract-norfolk-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? AI coding session transcripts are often multi-megabyte JSONL files that cannot be read directly into an agent's context window. This Skill extracts a compact, narrative-readable digest from a single session file so research agents can analyze sessions without loading raw logs. ## Core Features & Use Cases - Skeleton Extraction: Produces a narrative of user messages, assistant text, and collapsed tool-call summaries (3+ consecutive same-name calls are grouped), with framework wrapper tags stripped. - Error Signal Extraction: Isolates failed tool calls and non-zero-exit commands with timestamps, one error per block. - Multi-Platform Auto-Detection: Automatically detects Claude Code, Codex, or Cursor JSONL formats from the file structure. - Use Case: A session-research agent selects five relevant sessions from an inventory, then runs skeleton mode on each to compare conversation flows, and errors mode to find where tool calls failed. ## Quick Start Ask the agent to extract the conversation skeleton from a given session JSONL file path, optionally capping output with a head or tail line limit.

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 a conversation summary from a Claude Code session file?

Pipe the session JSONL file into the skeleton extraction script: cat session.jsonl | python3 scripts/extract-skeleton.py. It outputs user messages, assistant text, and collapsed tool-call summaries, ending with a _meta stats line.

How to find errors in Codex or Claude Code session logs?

Run the errors extraction mode, which filters the JSONL for failed tool calls. For Claude Code it finds tool results with is_error true; for Codex it finds exec_command_end events with non-zero exit codes or non-empty stderr.

Does session extraction work with Cursor agent transcripts?

Skeleton extraction works for Cursor transcripts, extracting user and assistant text plus tool calls. Error extraction returns nothing for Cursor because Cursor transcripts do not log tool results.

Why does the extraction output end with a _meta line?

The _meta JSON line reports processing statistics: total lines read, parse errors, and counts of user, assistant, tool, or error entries. Callers use it to decide whether partial extraction is acceptable or a deeper dive is needed.

What are the limitations of JSONL session extraction?

Thinking and reasoning blocks are excluded as internal content, tool outputs are summarized rather than returned in full, and text is truncated at 800 characters per block. Cursor sessions lack timestamps and tool result statuses.