Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Session Log Analyst

    1

    Search, mine, and summarize conversation history stored as session JSONL files: locate log roots, probe the record schema, extract user and assistant turns, and

    Free

    3 usesSecurity scanned
    Session Log Analyst

    Session Log Analyst

    Example session with this skill installed

    Find every time we talked about using Postgres in the last 30 days and show me which files have those logs.

    • Read your context and instructions
    • Compiled the session log analyst

    I searched ~/.hermes/sessions across 42 files from the last 30 days.

    Found matches

    • 2026-08-12-session.jsonl: "...decided to use Postgres for the vector store..."
    • 2026-08-15-session.jsonl: "...Postgres schema migration for the users table..."

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Finding specific information buried in months of agent logs is painful. Manually grepping through thousands of JSONL entries with inconsistent schemas leads to incomplete results and wasted time.

    What it does

    • Identifies log roots and probes varied record schemas across different agent frameworks.
    • Indexes conversation history by timestamp and session size for targeted retrieval.
    • Extracts specific user or assistant turns while filtering out noise and tool calls.
    • Performs keyword searches across entire corpora to locate specific decisions or references.
    • Aggregates usage statistics including message counts and costs grouped by date.

    Frameworks & tools

    Works with jq, find, and xargs. Compatible with Hermes, OpenClaw, and Claude projects log structures.

    Why this beats prompting it yourself

    Writing complex, schema-aware jq filters on the fly is error-prone. This skill handles schema variations like nested message objects and diverse timestamp formats, ensuring you get a clean table instead of a wall of JSON.

    Use cases

    • Recall specific technical decisions or promises made in conversations from last month.
    • Generate a summary of topics discussed across a specific workspace over a date range.
    • Audit LLM costs and message volume per day for a particular agent or project.
    • Locate every session where a specific database or framework was mentioned.

    Known limitations

    Requires logs to be in JSONL format. Compressed archives must be decompressed before analysis, and extremely large corpora should be sampled first.

    Requires logs in JSONL format. Binary or gzipped archives must be decompressed first. Large corpora should be sampled to maintain performance.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    3 uses

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 3 months ago

    • Free with an Agensi account

    Permissions

    Terminal / Shell
    Listed3 months ago

    What's inside

    Frequently Asked Questions

    This skill automates the process of querying large volumes of agent conversation logs by using schema-aware jq filters to extract specific messages, usage stats, and technical decisions without manual grepping.

    It is designed to handle schema variations from popular frameworks like Hermes, OpenClaw, and Claude projects, as well as custom JSONL structures with nested message objects.

    The skill requires your logs to be in JSONL format and relies on standard shell utilities like jq, find, and xargs for high-performance filtering.

    You will receive the optimized jq filter templates, the core logic for schema detection, and documentation on how to integrate the skill into your existing CLI or agent workflow.

    While it can process massive corpora, we recommend sampling extremely large datasets first or running the queries on a machine with sufficient memory for heavy jq operations.

    Yes, the tool is built to group data by date or session, allowing you to generate reports on message volume and estimated LLM costs for specific time periods.