session-logs

Parse JSONL session logs with jq to extract and summarize historical user messages.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/karaabd23-crypto/openclaw --skill session-logs-karaabd23-crypto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-logs
Source: https://github.com/karaabd23-crypto/openclaw/tree/main/skills/session-logs
Command: npx skills add https://github.com/karaabd23-crypto/openclaw --skill session-logs-karaabd23-crypto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you locate and analyze past conversations stored as session logs to understand context and history.

Core Features & Use Cases

  • Search across all sessions by date, user, or keyword.
  • Extract user and assistant messages, costs, and timestamps for analysis.
  • Use cases include understanding long-running conversations, auditing decisions, and preparing summaries.

Quick Start

Search your past session logs with jq to surface relevant context from older conversations.

Frequently Asked Questions about session-logs

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

FAQPage Schema
How do I search past conversation history stored in JSONL session logs?

To search JSONL session logs, you can parse the files using jq to locate and extract specific user and assistant messages based on keywords, dates, or user identifiers. This surfaces relevant context from older conversations.

Can I extract insights and summarize prior messages across multiple sessions?

Yes, you can summarize prior messages across multiple sessions by cross-referencing historical conversation records. This allows you to understand long-running dialogues and audit past decisions effectively.

What is the best way to parse JSONL conversation logs with jq?

Parsing JSONL conversation logs with jq involves applying the skill to index sessions and extract structured data like timestamps and costs. This approach presents user-friendly results while validating input and handling missing data.

Does this approach work for auditing decisions in long-running conversations?

Yes, auditing decisions in long-running conversations is a primary use case. By extracting user and assistant messages with their associated timestamps, you can analyze the history and context of past interactions.

How do I handle missing data when analyzing historical session logs?

When analyzing historical session logs, the process explicitly validates input and handles missing data to ensure accurate results. This prevents gaps in your JSONL records from disrupting the cross-referencing of prior messages.

What insights can I extract from conversation history logs?

From conversation history logs, you can extract user and assistant messages, cost data, and timestamps. These insights help prepare summaries and provide necessary context for current questions based on past interactions.