cc-history

Analyze Claude Code JSONL history logs to identify tool invocations and usage patterns.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/akiselev/qt-llm-template --skill cc-history-akiselev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-history
Source: https://github.com/akiselev/qt-llm-template/tree/main/.claude/skills/cc-history
Command: npx skills add https://github.com/akiselev/qt-llm-template --skill cc-history-akiselev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured guidance and reference material to analyze Claude Code conversation history files, turning verbose logs into actionable insights.

Core Features & Use Cases

  • Provides query patterns for locating token usage, tool invocations, and subagent conversations within JSONL history files.
  • Explains the expected file layout and encoding schemes used by Claude Code history storage to facilitate quick auditing.
  • Use Case: A data analyst reviews a session's history to quantify tool usage and message patterns across conversations.

Quick Start

Analyze a sample Claude Code history file to identify the most frequent tool invocations and large conversations.

Frequently Asked Questions about cc-history

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

FAQPage Schema
How do I analyze Claude Code conversation history files?

You analyze Claude Code conversation history by applying shell-based querying patterns to JSONL logs to extract and compare token usage, tool invocations, and subagent interactions across stored sessions.

What patterns can I use to extract tool usage from Claude Code JSONL logs?

You extract tool usage from JSONL logs by querying standardized fields for type, timestamp, and message usage to identify frequent tool invocations and quantify message patterns across conversations.

How do I compare token usage across multiple Claude Code sessions?

You compare token usage across sessions by applying consistent shell-based querying patterns across JSONL history files stored under the Claude history structure to surface usage insights and task flows.

What is the expected file layout for Claude Code history storage?

The expected file layout for Claude Code history storage uses consistent JSONL formatting with standardized fields for type, timestamp, and message usage to facilitate quick auditing and analysis.

Do I need a specific environment to parse Claude Code JSONL history files?

You need an environment supporting shell-based querying patterns to parse Claude Code JSONL history files, relying on consistent JSONL formatting and standardized fields for extraction.

Can I audit subagent interactions within Claude Code conversation logs?

Yes, you can audit subagent interactions within Claude Code conversation logs by applying query patterns to JSONL history files to surface subagent conversations and task flow interactions.