ce-session-extract

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

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Zeptiny/opencode-setup --skill ce-session-extract-zeptiny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-session-extract
Source: https://github.com/Zeptiny/opencode-setup/tree/main/skills/ce-session-extract
Command: npx skills add https://github.com/Zeptiny/opencode-setup --skill ce-session-extract-zeptiny

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the extraction of conversation skeletons or error signals from Claude Code, Codex, or Cursor session files, facilitating quick analysis and troubleshooting.

Core Features & Use Cases

  • Extract Conversation Skeleton: Provides a narrative of user messages, assistant text, and tool call summaries from a session file.
  • Extract Errors: Identifies and reports error signals from Claude Code, Codex, or Cursor session files.
  • Use Case: After a session-research agent selects specific sessions for analysis, this Skill can be used to quickly extract key information or error signals for further investigation.

Quick Start

Run the ce-session-extract skill with the path to the session file and the mode of extraction, e.g., ce-session-extract /path/to/session.jsonl skeleton.

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 skeleton from Claude Code or Cursor session files?

To extract a conversation skeleton from Claude Code or Cursor session files, run the extraction skill with the file path and 'skeleton' mode. It automatically parses different file formats to output user messages, assistant text, and tool call summaries.

Can I extract error signals from Codex or Cursor session logs for debugging?

Yes, you can extract error signals from Codex or Cursor session logs by running the extraction skill in error mode. It identifies and reports error signals from the session file to facilitate quick troubleshooting and post-session analysis.

What is a session file conversation skeleton used for in post-session analysis?

A session file conversation skeleton is used to provide a structured narrative of user messages, assistant responses, and tool call summaries. It enables quick analysis and debugging by highlighting key information from past agent interactions.

Does this session extraction tool work with different AI agent session file formats?

Yes, the session extraction tool handles different file formats from Claude Code, Codex, and Cursor. It automatically parses the specific session file structure to extract both user messages and assistant responses accurately.

What is the best way to debug errors from a completed AI coding agent session?

The best way to debug errors from a completed AI coding agent session is to run an automated extraction tool in error mode against the session file. This isolates error signals from the conversation log for targeted troubleshooting.