insights
Show session analytics, learning patterns, correction trends, heatmaps, and productivity metrics. Computes stats from project memory and session history. Use when asking for stats, statistics, progress, how am I doing, coding history, or dashboard.
Best use case
insights is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Show session analytics, learning patterns, correction trends, heatmaps, and productivity metrics. Computes stats from project memory and session history. Use when asking for stats, statistics, progress, how am I doing, coding history, or dashboard.
Teams using insights should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/insights/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How insights Compares
| Feature / Agent | insights | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Show session analytics, learning patterns, correction trends, heatmaps, and productivity metrics. Computes stats from project memory and session history. Use when asking for stats, statistics, progress, how am I doing, coding history, or dashboard.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
Top AI Agents for Productivity
See the top AI agent skills for productivity, workflow automation, operational systems, documentation, and everyday task execution.
SKILL.md Source
# Session Insights
Surface patterns from learnings and session history.
## Trigger
Use when asking "show stats", "how am I doing", "analytics", "insights", "heatmap", or "correction rate".
## Data Sources
Gather data from these locations before computing metrics:
```bash
# Session history and learnings
cat .claude/LEARNED.md 2>/dev/null || cat CLAUDE.md | grep -A999 "LEARNED"
cat .claude/learning-log.md 2>/dev/null
# Session activity
git log --oneline --since="today" --author="$(git config user.name)"
git diff --stat
```
A **correction** is any instance where the user redirected, fixed, or overrode agent output during a session. Count `[LEARN]` entries and explicit correction markers in session history.
## What It Shows
### Session Summary
```
Session Insights
Duration: 47 min
Edits: 23 files modified
Corrections: 2 self-corrections applied
Learnings: 3 new patterns captured
Context: 62% used (safe)
```
### Learning Analytics
```
Learning Insights (42 total)
Top categories:
Testing 12 learnings (29%)
Navigation 8 learnings (19%)
Git 7 learnings (17%)
Quality 6 learnings (14%)
Most applied:
#12 [Testing] Run tests before commit — 15 times
#8 [Navigation] Confirm path for common names — 11 times
Stale learnings (never applied):
#15 [Editing] Prefer named exports — 0 times (45 days old)
```
### Correction Heatmap
```
Correction Heatmap
By category (all time):
████████████ Testing 34 corrections
████████ Navigation 22 corrections
██████ Git 18 corrections
████ Quality 12 corrections
Hot learnings (most corrected, least learned):
- [Testing] Mock external deps — corrected 8x, learned 0x
→ Consider: /learn-rule to capture this permanently
Cold learnings (learned but never applied):
- [Editing] Use named exports — learned 45 days ago, applied 0x
→ Consider removing if no longer relevant
```
### Productivity Metrics
```
Productivity (last 10 sessions)
Avg session: 35 min
Avg edits/session: 18
Correction rate: 12% (improving)
Learning capture: 2.1 per session
```
## Guardrails
- Use actual data from project memory and session history.
- Surface actionable suggestions, not just numbers.
- Flag recurring corrections that should become permanent rules.
- Identify stale learnings that may no longer be relevant.
## Output
Formatted analytics report with:
- Current session stats
- Category breakdown
- Most/least applied learnings
- Correction trends with suggestions
- Productivity metrics over timeRelated Skills
wrap-up
End-of-session ritual that audits changes, runs quality checks, captures learnings, and produces a session summary. Use when saying "wrap up", "done for the day", "finish coding", or ending a coding session.
thoroughness-scoring
Score every decision point with a Thoroughness Rating (1-10). AI makes the marginal cost of doing things properly near-zero — pick the higher-rated option every time. Includes scope checks to distinguish contained vs unbounded work.
sprint-status
Track parallel work sessions and prevent confusion across multiple Claude Code instances. Every major step ends with a status line. Every question re-states project, branch, and task.
smart-commit
Run quality gates, review staged changes for issues, and create a well-crafted conventional commit. Use when saying "commit", "git commit", "save my changes", or ready to commit after making changes.
session-handoff
Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off".
safe-mode
Prevent destructive operations using Claude Code hooks. Three modes — cautious (warn on dangerous commands), lockdown (restrict edits to one directory), and clear (remove restrictions). Uses PreToolUse matchers for Bash, Edit, and Write.
replay-learnings
Surface past learnings relevant to the current task before starting work. Searches correction history, recalls past mistakes, and applies prior patterns. Use when starting a task, saying "what do I know about", "previous mistakes", "lessons learned", or "remind me about".
pro-workflow
Complete AI coding workflow system. Orchestration patterns, 18 hook events, 5 agents, cross-agent support, reference guides, and searchable learnings. Works with Claude Code, Cursor, and 32+ agents.
permission-tuner
Analyze permission denial patterns and generate optimized alwaysAllow and alwaysDeny rules. Use when permission prompts are slowing you down or after sessions with many denials.
parallel-worktrees
Create and manage git worktrees for parallel coding sessions with zero dead time. Use when blocked on tests, builds, wanting to work on multiple branches, context switching, or exploring multiple approaches simultaneously.
orchestrate
Wire Commands, Agents, and Skills together for complex features. Use when building features that need research, planning, and implementation phases.
mcp-audit
Audit connected MCP servers for token overhead, redundancy, and security. Use when sessions feel slow or before adding new MCPs.