Skip to main content
skill CX Codex

conversation-analyzer — Claude Code skill: what it does

conversation-analyzer analyzes your local Claude Code session logs to detect recurring errors, repetitive prompts, and workflow bottlenecks.

Apache-2.0 249 installs ★ 697 updated 2026-07-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add mhattingpete/claude-skills-marketplace --skill conversation-analyzer -a claude-code
Open on GitHub

What conversation-analyzer does

The skill inspects ~/.claude/history.jsonl, reviewing the last 200 conversations by default. It categorizes user requests into bug fixes, feature additions, refactoring, and general queries. The output highlights which codebases take up the most effort, flags vague initial prompts, and maps out peak productivity hours.

Behind the scenes, it executes scripts/analyze_history.py to compile two separate summaries: conversation_analysis.txt with metrics and recommendations.txt with prioritized workflow adjustments. You can also run the script standalone using python3 analyze_history.py inside the script directory.

All parsing happens on your local machine without sending prompt histories to external servers. If Python 3 is missing or ~/.claude/history.jsonl does not exist, the script cannot generate reports.

What it helps with

  • spot repetitive manual prompts that could be turned into custom scripts
  • track recurring test failures and bug-fixing loops across projects
  • measure time distribution across features, refactoring, and investigations
  • identify high-productivity hours during agent-assisted development

Example prompts for the agent

  • Analyze my recent Claude Code conversations and find workflow bottlenecks
  • Review my session history and suggest repetitive tasks worth automating
  • Show me the breakdown of my requests across projects and task types

How to install conversation-analyzer

1Skills CLI (Vercel)

npx skills add mhattingpete/claude-skills-marketplace --skill conversation-analyzer -a claude-code

2Manually: put the files in place

~/.claude/skills/conversation-analyzer/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/conversation-analyzer/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about conversation-analyzer

How to install conversation-analyzer in Claude Code?

Run npx skills add mhattingpete/claude-skills-marketplace --skill conversation-analyzer -a claude-code in your terminal.

What does conversation-analyzer do?

It parses your local conversation log to break down request categories, recurring errors, and time patterns into actionable recommendations.

Does the skill transmit conversation logs externally?

No, all analysis runs through a local Python script directly on your device, ensuring your prompt data remains private.

Source text

SKILL.md · Apache-2.0
---
name: conversation-analyzer
description: Analyzes your Claude Code conversation history to identify patterns, common mistakes, and opportunities for workflow improvement. Use when user wants to understand usage patterns, optimize workflow, identify automation opportunities, or check if they're following best practices.
---

# Conversation Analyzer

Analyzes your Claude Code conversation history to identify patterns, common mistakes, and workflow improvement opportunities.

## When to Use

- "analyze my conversations"
- "review my Claude Code history"
- "what patterns do you see in my usage"
- "how can I improve my workflow"
- "am I using Claude Code effectively"

## What It Analyzes

1. **Request type distribution** (bug fixes, features, refactoring, queries, testing)
2. **Most active projects**
3. **Common error keywords**
4. **Time-of-day patterns**
5. **Repetitive tasks** (automation opportunities)
6. **Vague requests** causing back-and-forth
7. **Complex tasks** attempted without planning
8. **Recurring bugs/errors**

## Analysis Scope

Default: **Last 200 conversations** for recency and relevance.

## Methodology

### 1. Request Type Distribution
Categorizes by: bug fixes, feature additions, refactoring, information queries, testing, other.

### 2. Project Activity
Tracks which projects consume most time, identifies project-specific patterns.

### 3. Time Patterns
Hour-of-day usage distribution, identifies peak productivity times.

### 4. Common Mistakes
- **Vague requests**: Initial requests lacking context vs. acceptable follow-ups
- **Repeated fixes**: Same issues occurring multiple times
- **Complex tasks**: Multi-step requests without planning
- **Repetitive commands**: Manual tasks that could be automated

### 5. Error Analysis
Frequency of error-related requests, common error keywords, recurring problems.

### 6. Automation Opportunities
Identifies repeated exact requests, suggests skills, slash commands, or scripts.

## Output

Structured report with:
- **Statistics**: Request types, active projects, timing patterns
- **Patterns**: Common tasks, repetitive commands, complexity indicators
- **Issues**: Specific problems with examples
- **Recommendations**: Prioritized, actionable improvements

## Tools Used

- **Read**: Load history file (`~/.claude/history.jsonl`)
- **Write**: Create analysis reports if requested
- **Bash**: Execute Python analysis script
- **Direct analysis**: Parse JSON programmatically

## Analysis Script

Uses `scripts/analyze_history.py` for comprehensive analysis:

**Capabilities:**
- Loads and parses `~/.claude/history.jsonl`
- Analyzes patterns across multiple dimensions
- Identifies common mistakes and inefficiencies
- Generates actionable recommendations
- Outputs detailed reports

**Usage within skill:**
Runs automatically when user requests analysis.

**Standalone usage:**
```bash
cd ~/.claude/plugins/*/productivity-skills/conversation-analyzer/scripts
python3 analyze_history.py
```

Outputs:
- `conversation_analysis.txt` - Detailed pattern analysis
- `recommendations.txt` - Specific improvement suggestions

## Example Output

```
Analyzed last 200 conversations:
- 60% general tasks, 15% bug fixes, 13% feature additions
- Project "ultramerge" dominates 58% of activity
- Same test-fixing request made 8 times
- 19 multi-step requests without planning
- Peak productivity: 13:00-15:00

Recommendations:
- Use test-fixing skill for recurring test failures
- Create project-specific utilities for ultramerge
- Use feature-planning skill for complex requests
- Add tests to prevent recurring bugs
- Schedule complex work during peak hours
```

## Success Criteria

- User understands usage patterns
- Concrete, actionable recommendations
- Specific examples from history
- Prioritized by impact (quick wins vs long-term)
- User can immediately apply improvements

## Integration

- **feature-planning**: Implement recommended improvements
- **test-fixing**: Address recurring test failures
- **git-pushing**: Commit workflow improvements

## Privacy Note

All analysis happens locally. Conversation history never leaves user's machine.

© mhattingpete · Apache-2.0 · mhattingpete/claude-skills-marketplace

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set15

The whole set →
timeline-creator timeline-creator turns a project's tasks and dates into an interactive HTML timeline with Gantt bars, phases and milestones. Handy when a plan has to live in one file. CX Codex +1 337installs code-refactor code-refactor is a Claude Code skill for bulk code changes across files: renaming variables and functions, replacing deprecated patterns, and updating API calls. It automatically selects a mode that saves up to 90% of tokens for 10+ files. CX Codex +1 304installs feature-planning The feature-planning skill turns feature requests and complex changes into ordered implementation plans with concrete tasks. Use it before coding when the scope needs structure. CX Codex +1 297installs code-execution The code-execution skill runs Python locally for bulk file work, code analysis, transformations, and Git tasks. It fits large or multi-step workflows. CX Codex +1 294installs technical-doc-creator technical-doc-creator builds HTML documentation for APIs and systems with code samples, architecture diagrams, syntax highlighting, and workflow steps. CX Codex +1 221installs ensemble-solving ensemble-solving spawns three parallel subagents to explore diverse solutions, scores each approach against weighted criteria, and returns the best outcome with trade-offs. CX Codex +1 218installs project-bootstrapper project-bootstrapper — a skill for Claude Code, Cursor, Codex and other platforms that scaffolds a new project or levels up an existing one: directories, linter configs, tests, Git hooks, CI/CD and documentation. CX Codex +1 212installs code-transfer A skill for precise code transfer between files using line-based positioning. Useful when you need to move a function to another file, extract a class into a separate module, or insert code at a specific line number. CX Codex +1 173installs

Project sponsors

Companies that keep this analytics open