mine

To extract a topic from a JSONL session log, provide a keyword or session ID. Four parallel subagents scan messages, assistant actions, code changes, and connections to compile a structured report with frequency counts and timestamped findings.

Yes, you can mine session logs using just a keyword. The skill matches the keyword against the most recent session ID, performing case-insensitive matching and local timezone conversion to generate a detailed narrative overview.

Analyzing code changes and AI actions in session logs is best handled by parallel subagents. These agents simultaneously scan assistant actions, code modifications, and connection metadata to deliver concise, structured insights without writing to trace logs.

Session log mining fully supports searching by a specific session ID. Providing a session ID directs the four subagents to scan human messages and code changes within that exact session, outputting a compiled report with sector-specific findings.

A limitation when extracting topics from session JSONL files is that the skill processes only a single file at a time. It requires local timezone conversion and does not write extracted findings to trace logs, focusing solely on compiled report generation.