Agent skill · pskoett
learning-aggregator
[Beta] Cross-session analysis of accumulated .learnings/ files. Reads all entries, groups by pattern_key, computes recurrence across sessions, and outputs ranked promotion candidates. This is the outer loop's inspect step — it turns raw learning data into actionable gap reports. Use on a regular cadence (weekly, before major tasks, or at session start for critical projects). Can be invoked manually or scheduled.
What it needs
About 9k tokens when loaded.
What this skill does
Learning Aggregator Reads accumulated .learnings/ files across all sessions, finds patterns, and produces a ranked list of promotion candidates. This is the outer loop's inspect step. Without this skill, .learnings/ is a write-only log. Patterns accumulate but nobody synthesizes them. The same gap resurfaces two weeks later because no one looked. When to Use Weekly cadence — scheduled or manual, review accumulated learnings Before major tasks — check if the task area has known patterns After a burst of sessions — consolidate findings from a sprint or incident When an entry's Recurrence-Count reaches the promotion threshold (>= 3) — verify the candidate with full context What It Produces A gap report — a ranked list of patterns that have crossed (or are approaching) the promotion threshold, with evidence and recommended actions. Step 1: Read All Learning Files Read these files in .learnings/: File Contains ------ ---------- LEARNINGS.md Corrections, knowledge gaps, best practices, recurring patterns ERRORS.md Command failures, API errors, exceptions FEATUREREQUESTS.md Missing capabilities HEALS.md Verified runtime recoveries filed by self-healing — including Handoff blocks flagging recurring patterns ready for promotion Parse each entry's metadata: Pattern-Key — the stable deduplication key Recurrence-Count — how many times this pattern has been seen First-Seen / Last-Seen — date range Priority — low / medium / high / critical Status — pending / inprogress / resolved / wontfix / promoted / promotedtoskill (the writer's vocabulary; promotion readiness is computed from Recurrence-Count, not stored as a status) Area — frontend / backend / infra / tests / docs / config Related Files — which parts of the codebase are affected Source — conversation / error / userfeedback / simplify-and-harden Tags — free-form labels Task-ID, Session-ID, Occurrence-ID, Source-Ref, Copied-From — optional provenance fields from newer writers Step 2: Group and Aggregate Build canonical occurre …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pskoett/learning-aggregator--b9ade8