session-logs

Parse JSONL session logs with jq to extract historical conversation data.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kulharir7/karya --skill session-logs-kulharir7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-logs
Source: https://github.com/kulharir7/karya/tree/main/workspace/plugins/session-logs
Command: npx skills add https://github.com/kulharir7/karya --skill session-logs-kulharir7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrieve and interpret historical conversations stored in session logs on your machine, enabling context-aware decision making across agent interactions.

Core Features & Use Cases

  • Query past conversations by date, session ID, or keyword to understand context and evolution.
  • Generate concise summaries of long discussions to speed up context switching.
  • Audit decisions by tracing user prompts and assistant responses across sessions.

Quick Start

Search your session history for a keyword or date and summarize the relevant messages.

Frequently Asked Questions about session-logs

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

FAQPage Schema
How do I search historical session logs stored in JSONL format?

Search historical session logs by using jq to parse local JSONL files stored under the ~/.nivbot/agents/<agentId>/sessions directory. This process matches keywords, dates, or session IDs to return structured results suitable for summarization.

What is the best way to summarize past conversations from local agent sessions?

Summarize past conversations by querying the local JSONL session history for specific dates or keywords. The tool extracts relevant messages from agent sessions to generate concise summaries that speed up context switching.

Can I audit decision histories by tracing prompts and responses across sessions?

Audit decision histories by tracing user prompts and assistant responses across stored sessions. The tool queries local JSONL logs to interpret historical conversations, enabling context-aware review of prior agent interactions.

Does session log searching require any specific environment setup or dependencies?

Session log searching requires local JSONL files within the ~/.nivbot/agents/<agentId>/sessions directory and uses jq to parse the data. No external dependencies are needed beyond the local log files and jq.

How do I extract insights from multiple agent sessions using keyword queries?

Extract insights from multiple agent sessions by running keyword queries against local JSONL logs. The tool applies jq to parse the session history and returns structured results that highlight relevant context across interactions.