Session Insights
This skill should be used when the user asks to "analyze sessions", "review my Claude usage", "session insights", "what have I been working on", "improve my workflow", "analyze conversation history", or mentions reviewing past Claude Code sessions. Routes to /session-review or /session-stats commands.
What this skill does
# Session Insights
Analyze your Claude Code conversation history with interactive selection, deep drill-down, and workflow improvement generation.
## What This Plugin Does
Session Insights provides programmatic analysis of your local Claude Code session data:
- **Interactive browsing** — select specific projects, sessions, or date ranges to analyze
- **Deep drill-down** — extract turn-by-turn detail from specific sessions at configurable detail levels
- **Workflow improvements** — turn analysis into concrete CLAUDE.md additions, commands, skills, or hooks
- **Usage statistics** — cross-session aggregate stats on tool usage, token consumption, and activity patterns
### How It Differs from Built-in `/insights`
The built-in `/insights` command generates a broad HTML report across up to 50 sessions with Haiku-level analysis. Session Insights complements it with:
1. **Interactive session selection** instead of automatic sampling
2. **Opus-level depth** for focused analysis of specific sessions
3. **Actionable output** — generates CLAUDE.md improvements, not just reports
4. **Programmatic parsing** — Node.js scripts keep raw JSONL out of context (handles 1GB+ data)
## Available Commands
### `/session-review` — Deep Analysis Workflow
A 6-phase interactive workflow:
1. **Discovery** — Browse projects and usage overview
2. **Session Selection** — Pick specific sessions or date ranges
3. **Analysis** — 3 parallel agents analyze insights, improvements, and patterns
4. **Synthesis** — Consolidated report with statistics dashboard
5. **Drill-Down** — Interactive deep-dive into specific findings
6. **Workflow Improvement** — Generate CLAUDE.md additions and automation suggestions
### `/session-stats` — Quick Dashboard
Fast overview of usage statistics:
- Total sessions, projects, messages, date range
- Top projects by session count
- Token usage summary
- Most-used tools
- Activity patterns by day and hour
## How Scripts Work
All analysis uses streaming Node.js scripts at `${CLAUDE_PLUGIN_ROOT}/scripts/`:
| Script | Purpose |
|--------|---------|
| `list-projects.js` | Enumerate projects with session counts and sizes |
| `list-sessions.js` | List sessions for a project with metadata |
| `extract-session.js` | Structured turn-by-turn summary with detail levels (low/medium/high) |
| `extract-history.js` | Parse history.jsonl with filters |
| `aggregate-stats.js` | Cross-session aggregate statistics |
Scripts read JSONL files via `readline` streaming — they never load entire files into memory. Output is JSON to stdout.
**IMPORTANT**: Always use scripts to parse session data. Never read `.jsonl` files directly into context — they can be megabytes in size and would consume the entire context window.
## Data Format
- **`~/.claude/history.jsonl`** — One line per user message with `{display, sessionId, project, timestamp}`
- **`~/.claude/projects/<dash-path>/<session-id>.jsonl`** — Full transcripts with `user`, `assistant`, `progress`, `file-history-snapshot` types
- Project directories use dashes for path separators (e.g., `-home-user-Source-project`)
## Privacy
All analysis is performed locally. No session data leaves your machine. Scripts read from `~/.claude/` and output structured JSON — the raw conversation content stays in the JSONL files.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.