Show session analytics, learning patterns, correction trends, heatmaps, and productivity metrics. Use when wanting to understand your coding patterns over time.
80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Surface patterns from learnings and session history.
Use when asking "show stats", "how am I doing", "analytics", "insights", "heatmap", or "correction rate".
Session Insights
Duration: 47 min
Edits: 23 files modified
Corrections: 2 self-corrections applied
Learnings: 3 new patterns captured
Context: 62% used (safe)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
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 relevantProductivity (last 10 sessions)
Avg session: 35 min
Avg edits/session: 18
Correction rate: 12% (improving)
Learning capture: 2.1 per sessionFormatted analytics report with:
aad0763
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.