cc-insights

To analyze Claude Code interaction history, this skill reads local history.jsonl files and timeline data to extract project activity, hourly distribution, and prompt-length metrics. It outputs structured metrics and a narrative summary to reveal usage trends.

Yes, you can automatically archive chat sessions from Claude Code history into organized Markdown files. The skill applies time-based indexing to the archived interaction data, creating structured records for reporting.

A Claude Code insights report includes per-project activity, hourly distribution, and prompt-length metrics. These analytics surface usage patterns and project hotspots from your archived timeline data.

No external dependencies are required to process local history files. The skill uses internal scripts and references to read history.jsonl and timeline data directly, generating structured metrics without external packages.

The best way to generate an executive summary from archived Claude Code projects is to apply the skill's deep analytics to your timeline data. It processes interaction history to produce narrative summaries suitable for governance and optimization.

You need to archive Claude Code interactions to establish a persistent, organized record of timeline data. This archived history allows the skill to accurately compute per-project activity and reveal usage hotspots over time.