session-reader

Parse and analyze pi agent session JSONL files with structured summaries.

437|40|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/HazAT/pi-config --skill session-reader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-reader
Source: https://github.com/HazAT/pi-config/tree/main/skills/session-reader
Command: npx skills add https://github.com/HazAT/pi-config --skill session-reader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows you to efficiently read and analyze pi agent session JSONL files, making it easy to understand past interactions, debug issues, and track agent performance.

Core Features & Use Cases

  • Session Overview: Get a high-level summary of session metadata, turn count, and tool usage.
  • Detailed Analysis: View conversation history, tool calls and results, cost breakdowns, and subagent delegations.
  • Use Case: When asked to "review the last session for project X", you can use this skill to quickly get an overview, then drill down into specific turns or subagent actions to understand what happened and why.

Quick Start

Use the session-reader skill to get an overview of the session file located at ~/.pi/agent/sessions/my-project/2023-10-27T10-00-00Z_abc.jsonl.

Frequently Asked Questions about session-reader

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

FAQPage Schema
How do I analyze agent session JSONL files for debugging?

To review agent behavior, parse the JSONL session log to examine conversation turns, tool interactions, and subagent execution histories. This provides structured summaries to debug issues and understand past agent performance.

What is the best way to get a session overview from JSONL logs?

Getting a session overview from JSONL logs involves parsing the file to extract high-level metadata, turn counts, and tool usage. This provides a structured summary of the session history without manual line-by-line reading.

Can I view cost breakdowns and tool calls from a pi agent session?

Yes, viewing cost breakdowns and tool calls from a pi agent session requires parsing the JSONL output. The parsed data enables detailed examination of specific tool results and cost analysis for each interaction.

How do I track subagent execution logs within a session file?

Tracking subagent execution logs within a session file requires parsing the JSONL structure to isolate subagent delegations. This allows you to drill down into specific turns and understand delegated actions and results.

Does this session log analysis approach require any external dependencies?

No, this session log analysis approach requires no external dependencies to function. It operates independently using internal scripts and references to parse and review the JSONL agent session files.