Stats
Actions
Tags
Detect when the user asks about workflow patterns, friction points, automation opportunities, or time loss in their Claude Code usage. Checks session analysis state and routes to /session-history-analyzer:analyze for full analysis.
How this skill is triggered — by the user, by Claude, or both
Slash command
/session-history-analyzer:analyzeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Triggered when the user asks about workflow patterns, friction, or automation opportunities.
Triggered when the user asks about workflow patterns, friction, or automation opportunities.
Check current analysis state:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.sh summary
Discover available sessions:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/discover-sessions.sh
Summarize what's available:
Route to /session-history-analyzer:analyze for a full analysis run. Do not attempt to parse sessions directly from this skill.
npx claudepluginhub st0nefish/agent-toolkit --plugin session-history-analyzerAnalyzes Claude Code sessions using MCP classifiers to detect usage patterns like correction spirals, rates severity, and provides concrete workflow improvements with metrics and advice.
Reviews recent Claude Code sessions (default last 5) in the current project for patterns, using parallel conversation-reviewer agents per session and cross-session synthesis.
Analyzes Claude Code session logs to extract tool usage stats, thinking blocks, error patterns, debug trajectories, and generate actionable productivity recommendations. Provides cc-session CLI for overviews, timelines, searches.