Agent skill · software engineering · aiskillstore

extract-transcripts

Extract readable transcripts from Claude Code and Codex CLI session JSONL files

Why this skill is useful

Adds multiple executable scripts for extracting and indexing transcripts from Claude Code and Codex CLI session JSONL files, which are not commonly available in public documentation.

What it needs

Requires duckdb installed locally. About 1k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.

What this skill does

Extract Transcripts Extracts readable markdown transcripts from Claude Code and Codex CLI session JSONL files. Scripts Claude Code Sessions Options: --include-tools: Include tool calls and results --include-thinking: Include Claude's thinking blocks --all: Process all .jsonl files in directory -o, --output: Output file path (default: stdout) --summary: Only output brief summary --skip-empty: Skip empty and warmup-only sessions --min-messages N: Minimum messages for --skip-empty (default: 2) Codex CLI Sessions Session File Locations Claude Code Sessions: ~/.claude/projects/<project-path>/<session-id>.jsonl Codex CLI Sessions: ~/.codex/sessions/<sessionid>/rollout.jsonl History: ~/.codex/history.jsonl DuckDB-Based Transcript Index For querying across many sessions, use the DuckDB-based indexer: Requirements: DuckDB (pip install duckdb) Database location: ~/.claude/transcript-index/sessions.duckdb Output Format Transcripts are formatted as markdown with: Session metadata (date, duration, model, working directory, git branch) User messages prefixed with ## User Assistant responses prefixed with ## Assistant Tool calls in code blocks (if --include-tools) Thinking in blockquotes (if --include-thinking) Tool usage summary for Codex sessions

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills aiskillstore/extract-transcripts

View the source on GitHub

Browse the @skills marketplace