rohitg00/insights
skills/insights/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add rohitg00/pro-workflow insightsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 19, 2026, 6:07 AM170.5s1 file scanned
SKILL.md
- name:
- insights
- description:
- 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.
- user-invocable:
- true
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
Related Skills
rohitg00/writing-guidelines
documentation
VerifiedTrustedCommunity
Apply clear-writing standards to any prose the agent produces - READMEs, docs, UI copy, error messages, commit and PR text, release notes. Use when writing or editing documentation, interface copy, or any text a human will read. Says "write the README", "improve this copy", "draft the docs", "word this error".
2,619SKILL.mdUpdated Jul 19, 2026
rohitg00/tdd
development
VerifiedTrustedCommunity
Drive a change through a red-green-refactor loop - failing test first, minimal code to pass, then clean up. Use when implementing a feature or fixing a bug where correctness matters and a test can pin the behavior. Says "TDD", "test first", "red green refactor", "write the test first".
2,619SKILL.mdUpdated Jul 19, 2026
rohitg00/skill-router
tools
VerifiedTrustedCommunity
The index of every pro-workflow skill and command, grouped by job, with when to reach for each and whether it is human-run or auto-triggered. Use when you are not sure which skill fits, want the full map, or ask "what can this do", "which skill for X", "list the workflow".
2,619SKILL.mdUpdated Jul 19, 2026
rohitg00/improve-architecture
development
VerifiedTrustedCommunity
Audit an area of the codebase and propose the smallest structural moves that improve it - untangle boundaries, kill duplication, fix seams, break cycles. Produces a prioritized plan and decision records, not a rewrite. Use when a codebase feels tangled, hard to change, or is becoming a ball of mud, or when asked to improve or refactor architecture.
2,619SKILL.mdUpdated Jul 19, 2026