jsonl-chronicle-extractor

Extract regex-matching narrative blocks from JSONL message content.

1|2|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/jgwill/dotagents --skill jsonl-chronicle-extractor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jsonl-chronicle-extractor
Source: https://github.com/jgwill/dotagents/tree/main/skills/jsonl-chronicle-extractor
Command: npx skills add https://github.com/jgwill/dotagents --skill jsonl-chronicle-extractor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It eliminates the manual effort of searching through large JSONL log files to locate multi-line “Session Chronicle” narrative blocks buried inside nested text fields.

Core Features & Use Cases

  • Targeted chronicle extraction: Parses JSONL line-by-line, inspects nested message.content[].text fields, and extracts entries whose text matches a regex.
  • Regex-driven selection: Supports JavaScript-compatible regular expressions so you can precisely select a specific chronicle header (e.g., varying “Feb/February” spellings).
  • Works for structured logs: Useful for extracting narrative blocks from progressive response logs or other JSONL exports that follow the expected message/content structure.

Quick Start

Run the script to extract all matching chronicles from a JSONL file by providing the file path and the regex pattern for the chronicle header.

Frequently Asked Questions about jsonl-chronicle-extractor

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

FAQPage Schema
How do I extract specific text blocks from JSONL logs?

You can extract targeted text blocks from JSONL logs by streaming the file line-by-line, parsing each JSON object, and traversing nested message content fields to filter matches using a regular expression pattern.

What's the best way to parse session chronicles from progressive response exports?

Parsing session chronicles from progressive response exports requires reading the JSONL file, inspecting nested message.content text blocks, and concatenating entries that match a specific chronicle header regex separated by dashes.

Can I use a custom regex to filter nested message content in JSONL files?

Yes, you can use a custom JavaScript-compatible regular expression to filter nested message content in JSONL files, allowing you to precisely select varying text patterns like different date spellings in chronicle headers.

How does regex-driven log parsing work for structured JSONL files?

Regex-driven log parsing for structured JSONL files works by applying a regular expression to nested message.content text blocks during line-by-line streaming, isolating specific narrative blocks from the broader log data.

Do I need Node.js dependencies to extract narrative blocks from JSONL logs?

No external dependencies are required to extract narrative blocks from JSONL logs, as the extraction relies solely on standard streaming JSONL reading and native JSON parsing to locate and concatenate matching text.