session-logs

Search and analyze historical JSONL session logs with ripgrep and jq.

Updated May 7, 2026
One-click install
npx skills add https://github.com/MOODMNKY-LLC/mnky-atlas --skill session-logs-moodmnky-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-logs
Source: https://github.com/MOODMNKY-LLC/mnky-atlas/tree/main/skills/session-logs
Command: npx skills add https://github.com/MOODMNKY-LLC/mnky-atlas --skill session-logs-moodmnky-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the frustration of losing access to historical conversation context when it falls out of the active memory window, letting you retrieve details from prior chats, parent conversations, and older interactions without manual file searching.

Core Features & Use Cases

  • Cross-session log search: Find specific keywords or phrases across all stored session JSONL files.
  • Targeted data extraction: Pull only user messages, assistant responses, tool calls, or cost data from individual session logs.
  • Usage analytics: Generate message counts, token usage, and cost summaries for past conversations.
  • Use Case: If a user asks what was discussed about the new product launch in conversations from 3 weeks ago, use this Skill to quickly locate and extract all relevant context from the corresponding session logs.

Quick Start

Use the session-logs skill to find all messages from last month's sessions that mention the Q4 marketing strategy.

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 logs that are no longer in active memory?

To search past conversation logs that fell out of the active memory window, you can parse and filter historical JSONL session files to retrieve specific keywords, user messages, or assistant responses from prior chats.

Do I need jq and ripgrep to analyze JSONL session logs?

Yes, you need jq and ripgrep command-line tools installed to efficiently parse, filter, and search JSONL session files for retrieving targeted historical conversation context and usage analytics.

Can I extract token usage and cost data from historical session logs?

Yes, you can extract token usage and cost data from historical session logs by parsing the JSONL files to generate message counts and cost summaries for past conversations.

What is the best way to find context from a parent conversation stored weeks ago?

The best way to find context from a parent conversation stored weeks ago is cross-session log searching, which scans stored JSONL files to locate specific keywords or phrases from older interactions.

Does retrieving context from JSONL conversation logs work for individual session files?

Yes, retrieving context works for individual session files by applying targeted data extraction to pull only user messages, assistant responses, tool calls, or cost data from the specific JSONL log.

What are the limitations of searching historical chat context with command-line tools?

A limitation of searching historical chat context with command-line tools is that this approach requires local JSONL files to be present and organized, meaning context cannot be retrieved if logs were not properly saved.