SkillAgentSearch skills...

conversation-analyzer

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

Install / Use

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

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

81/100

Category

Automation

Supported Platforms

Claude Code

Our assessment of conversation-analyzer

conversation-analyzer scores 81/100 on our quality scale, 2421st of 2,769 Automation skills we index.

Its SKILL.md is 4.0 KB long, well organised into 18 sections with 2 code examples: a solid amount of guidance for an agent.

It has 678 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
12/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 98/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

conversation-analyzer compared with similar skills

All 4 of these similar skills score higher than conversation-analyzer; compare them before choosing.

SkillScoreStarsUpdatedFormat
conversation-analyzer (this skill)by mhattingpete816784mo agoSKILL.md
Agent-Reachby Panniantong100112.7k9d agoCLAUDE.md
rufloby ruvnet10082.0ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.9k8d agoCLAUDE.md
Scraplingby D4Vinci100103.9ktodayMCP Server

Frequently asked questions

How do I install conversation-analyzer?
Run npx skills add mhattingpete/claude-skills-marketplace --skill conversation-analyzer. The install tabs above show the steps for each supported agent.
Which AI agents does conversation-analyzer work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is conversation-analyzer safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 98/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is conversation-analyzer still maintained?
The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

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:

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.

Related Skills

View on GitHub
GitHub Stars678
CategoryAutomation
Updated3mo ago
Forks96

Languages

HTML

Trust signals

98/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info