session-insights

Analyze Claude Code session metrics and logs to identify usage patterns.

8|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/luiseiman/dotforge --skill session-insights-luiseiman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-insights
Source: https://github.com/luiseiman/dotforge/tree/main/skills/session-insights
Command: npx skills add https://github.com/luiseiman/dotforge --skill session-insights-luiseiman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze Claude Code session data to identify usage patterns, metrics, and improvement recommendations.

Core Features & Use Cases

  • Data gathering from metrics, errors, git history, agent memory, and registry trends to build a comprehensive view.
  • Metric computation to compute session counts, average files touched, hook blocks, rule coverage trends, and error rate.
  • Recommendations & reporting to generate actionable steps, create practices, and inform strategy.

Quick Start

Run the session-insights analysis to generate a comprehensive report of Claude Code usage patterns and recommendations.

Frequently Asked Questions about session-insights

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

FAQPage Schema
How do I analyze Claude Code session data for usage patterns and error metrics?

To analyze Claude Code session data, aggregate metrics, error logs, Git history, agent-memory, and registry trends to compute session counts, average files touched, hook blocks, rule coverage trends, and error rates for actionable team reporting.

What metrics can I extract from Claude Code session logs?

You can extract session counts, average files touched, hook blocks, rule coverage trends, and error rates from Claude Code session logs to identify performance signals and reveal optimization opportunities.

How do I generate actionable recommendations from Claude Code agent-memory and Git history?

Generate actionable recommendations by aggregating Git history and agent-memory data to identify performance signals, validate trend analysis against guardrails, and output structured reporting suitable for team adoption.

What is the best way to monitor ongoing performance trends in Claude Code sessions?

The best way to monitor ongoing performance trends is applying data aggregation and trend analysis across session metrics, error logs, and registry trends to support both retroactive analysis and continuous monitoring.

Does session insights analysis require any external dependencies or specific data formats?

Session insights analysis requires no external dependencies, operating directly on Claude Code session metrics, error logs, Git history, agent-memory, and registry trends to ensure structured outputs meet validation and guardrails.