session-logs

To search past conversation history stored in JSONL files, you can use this Skill to parse and filter session logs with `jq` and `rg`. It enables retrieving historical context, user queries, and assistant responses from previous interactions efficiently.

The best way to analyze session data and message costs is by using `jq` and `rg` to parse JSONL session logs. This approach allows you to examine message counts, tool usage, and cost data within individual past sessions.

Yes, you need `jq` and `rg` installed, as the Skill requires both command-line tools to parse and filter JSONL session data efficiently. They are necessary dependencies for retrieving historical context.

Yes, you can retrieve historical context from a specific date by filtering your session logs. The Skill processes JSONL files to locate information such as user queries and assistant responses from previous interactions on that date.

You need to search JSONL session logs when a decision made in a previous conversation is not readily available in current memory. This allows you to recall specific information and historical context from parent conversations.

A limitation of using `rg` and `jq` for conversation history analysis is that the session logs must be stored in JSONL format. The Skill cannot parse or filter session data from other file formats or unsupported structures.