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.
View on GitHubmhattingpete/claude-skills-marketplace
productivity-skills
productivity-skills-plugin/skills/conversation-analyzer/SKILL.md
January 23, 2026
Select agents to install to:
npx add-skill https://github.com/mhattingpete/claude-skills-marketplace/blob/main/productivity-skills-plugin/skills/conversation-analyzer/SKILL.md -a claude-code --skill conversation-analyzerInstallation paths:
.claude/skills/conversation-analyzer/# 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`) - **Writ