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.
Analyzes your Claude Code conversation history to identify usage patterns, common mistakes, and workflow improvement opportunities. Use when you want to understand your usage patterns, optimize workflows, identify automation opportunities, or check if you're following best practices.
/plugin marketplace add mhattingpete/claude-skills-marketplace/plugin install productivity-skills@mhattingpete-claude-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
scripts/analyze_history.pyAnalyzes your Claude Code conversation history to identify patterns, common mistakes, and workflow improvement opportunities.
Default: Last 200 conversations for recency and relevance.
Categorizes by: bug fixes, feature additions, refactoring, information queries, testing, other.
Tracks which projects consume most time, identifies project-specific patterns.
Hour-of-day usage distribution, identifies peak productivity times.
Frequency of error-related requests, common error keywords, recurring problems.
Identifies repeated exact requests, suggests skills, slash commands, or scripts.
Structured report with:
~/.claude/history.jsonl)Uses scripts/analyze_history.py for comprehensive analysis:
Capabilities:
~/.claude/history.jsonlUsage 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 analysisrecommendations.txt - Specific improvement suggestionsAnalyzed 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
All analysis happens locally. Conversation history never leaves user's machine.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.