← ClaudeAtlas

transcript-analysislisted

Analyze Cowork session transcripts for recurring narrative patterns — repeated instructions, planning loops, failure patterns, decision re-litigation, and knowledge re-establishment. Produces a structured report with CLAUDE.md candidates, unresolved loops, and pattern frequency data. Use this skill when the user wants to review what keeps repeating across sessions, extract lessons from past work, audit their collaboration patterns, or identify rules that should be encoded permanently. Triggers on: transcript analysis, session analysis, narrative analysis, what keeps repeating, review our sessions, cowork analysis, pattern analysis, what should go in CLAUDE.md, extract lessons, session retrospective, retro, session patterns.
BryceEWatson/claude-global-skills · ★ 0 · AI & Automation · score 75
Install: claude install-skill BryceEWatson/claude-global-skills
# Transcript Analysis — Recurring Narrative Pattern Mining Analyze all Cowork session transcripts for the current project to identify recurring patterns — repeated instructions, planning loops, failure regressions, decision re-litigation, and knowledge that has to be rebuilt each session. Produces a structured report with actionable recommendations. ## Why This Skill Exists After enough sessions, behavioral patterns emerge that are invisible within any single conversation: rules the user keeps re-stating, mistakes that keep recurring, planning discussions that never resolve, and context that has to be rebuilt every time. This skill surfaces those patterns so the important ones can be encoded into CLAUDE.md (or skills) and the rest can be consciously accepted or resolved. ## When to Use This Skill - The user asks "what keeps repeating across our sessions?" - After a significant milestone (10+ sessions, major feature complete, quarterly review) - When CLAUDE.md feels stale or incomplete - When the user suspects the same mistakes keep happening - Before a major architecture or workflow change (to understand current pain points) ## Inputs - **Project folder path** — defaults to the current working directory. Used to filter sessions by `userSelectedFolders` in Cowork manifests. - **Optional: keyword filter** — additional terms to match beyond folder path (e.g., brand names, product terms, tool names). The user can provide these or you can derive them from the project's CLAU