conversation-analyzer
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.
What this skill does
# 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.
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.