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.
- Installs
- 167
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/rohitg00/pro-workflow --skill insights- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads insights automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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:
# 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 time
FAQ
What does the insights 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.
How do I install insights?
Run npx skills add https://github.com/rohitg00/pro-workflow --skill insights in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/insights/ (personal) or .claude/skills/insights/ (project).
Which AI agents can use insights?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is insights safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains insights?
It is published by rohitg00 in rohitg00/pro-workflow. It has 167 recorded installs.
More from rohitg00/pro-workflow
token-efficiency
rohitg00/pro-workflow
Reduce token waste by 40-60% through anti-sycophancy rules, tool-call budgets, one-pass coding, task profiles, and read-before-write enforcement. Inspired by drona23/claude-token-efficient.
pro-workflow
rohitg00/pro-workflow
Complete AI coding workflow system. Orchestration patterns, 18 hook events, 8 agents, cross-agent support, reference guides, and searchable learnings. Works with Claude Code, Cursor, and 32+ agents.
wrap-up
rohitg00/pro-workflow
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.
deslop
rohitg00/pro-workflow
Remove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or when reviewing a skill before promoting it.
learn-rule
rohitg00/pro-workflow
Capture a correction or lesson as a persistent learning rule with category, mistake, and correction. Stores, categorises, and retrieves rules for future sessions. Use after mistakes or when the user says "remember this", "don't forget", "note this", or "learn from this".
session-handoff
rohitg00/pro-workflow
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".
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.