Conversation Analysis
Signal extraction → pattern detection → behavioral insights.
- User requests conversation analysis
- Identifying frustration, success, or workflow patterns
- Extracting user preferences and requirements
- Understanding task evolution and iterations
NOT for: real-time monitoring, content generation, single message analysis
| Type |
Subtype |
Indicators |
| Success |
Explicit Praise |
"Perfect!", "Exactly what I needed", exclamation marks |
| Success |
Continuation |
"Now do the same for...", building on prior work |
| Success |
Adoption |
User implements suggestion without modification |
| Success |
Acceptance |
"Looks good", "Ship it", "Merge this" |
| Frustration |
Correction |
"No, I meant...", "That's wrong", "Do X instead" |
| Frustration |
Reversion |
User undoes agent changes, "Go back" |
| Frustration |
Repetition |
Same request 2+ times, escalating specificity |
| Frustration |
Explicit |
"This isn't working", "Why did you...", accusatory tone |
| Workflow |
Sequence |
"First...", "Then...", "Finally...", numbered lists |
| Workflow |
Transition |
"Now that X is done, let's Y", stage changes |
| Workflow |
Tool Chain |
Recurring tool usage patterns (Read → Edit → Bash) |
| Workflow |
Context Switch |
Abrupt topic changes, no transition language |
| Request |
Prohibition |
"Don't use X", "Never do Y", "Avoid Z" |
| Request |
Requirement |
"Always check...", "Make sure to...", "You must..." |
| Request |
Preference |
"I prefer...", "It's better to...", comparative language |
| Request |
Conditional |
"If X then Y", "When A, do B", situational rules |
Confidence levels:
- High (0.8–1.0): Explicit keywords match taxonomy, no ambiguity, strong context
- Medium (0.5–0.79): Implicit signal, partial context, minor ambiguity
- Low (0.2–0.49): Ambiguous language, weak context, borderline classification
Load the maintain-tasks skill for stage tracking. Stages advance only, never regress.
| Stage |
Trigger |
activeForm |
| Parse Input |
Session start |
"Parsing input" |
| Extract Signals |
Scope validated |
"Extracting signals" |
| Detect Patterns |
Signals extracted |
"Detecting patterns" |
| Synthesize Report |
Patterns detected |
"Synthesizing report" |
Task format:
- Parse Input { scope description }
- Extract Signals { from N messages }
- Detect Patterns { category focus }
- Synthesize Report { output format }
Edge cases:
- Small scope (<5 messages): Skip Extract Signals, jump to Synthesize
- Re-analysis: Resume at Detect Patterns
- Narrow focus (single signal type): Skip Detect Patterns
Workflow:
- Start: Create Parse Input
in_progress
- Transition: Mark current
completed, add next in_progress
- After delivery: Mark Synthesize Report
completed
Define Scope
- Message range (all, recent N, date range)
- Actors (user only, agent only, both)
- Exclusions (system messages, tool outputs, code blocks)
- Mark Parse Input
completed, create Extract Signals in_progress
Extract Signals
- Scan messages for signal keywords
- Match against taxonomy
- Assign confidence (high/medium/low)
- Record: type, subtype, message_id, timestamp, quote, context
- Mark Extract Signals
completed, create Detect Patterns in_progress
Detect Patterns
- Group signals by type/subtype
- Find clusters (3+ related signals)
- Identify evolution (signal changes over time)
- Track repetition (recurring themes)
- Spot correlations (tool chains, workflows)
- Mark Detect Patterns
completed, create Synthesize Report in_progress
Output
- Generate JSON with signals, patterns, summary
- Include confidence, recommendations, action items
- Append
△ Caveats if gaps exist
- Mark Synthesize Report
completed
Behavioral patterns from signal clusters:
| Pattern |
Detection |
Confidence |
| Repetition |
Same signal 3+ times |
Strong: 5+ signals |
| Evolution |
Signal type changes over time |
Moderate: 3-4 signals |
| Preferences |
Consistent request signals |
Strong: across sessions |
| Tool Chains |
Recurring tool sequences (5+ times) |
High: frequent use |
| Problem Areas |
Clustered frustration signals |
Strong: 3+ in same topic |
Temporal patterns:
- Escalation: Increasing frustration/stronger requirements
- De-escalation: Frustration → success transition
- Cyclical: Same issue recurs across sessions
JSON structure:
{
"analysis": {
"scope": {
"message_count": N,
"date_range": "YYYY-MM-DD to YYYY-MM-DD",
"actors": ["user", "agent"]
},
"signals": [
{
"type": "success|frustration|workflow|request",
"subtype": "specific_subtype",
"message_id": "msg_123",
"timestamp": "ISO8601",
"quote": "exact text",
"confidence": "high|medium|low",
"context": "brief explanation"
}
],
"patterns": [
{
"pattern_type": "repetition|evolution|preference|tool_chain",
"category": "success|frustration|workflow|request",
"description": "pattern summary",
"occurrences": N,
"confidence": "strong|moderate|weak",
"first_seen": "ISO8601",
"last_seen": "ISO8601",
"recommendation": "actionable next step"
}
],
"summary": {
"total_signals": N,
"by_type": { "success": N, "frustration": N, ... },
"key_insights": ["insight 1", "insight 2"],
"action_items": ["item 1", "item 2"]
}
}
}
ALWAYS:
- Create Parse Input at session start
- Update todos at stage transitions
- Include confidence levels for all signals
- Support patterns with 2+ signals minimum
- Mark Synthesize Report
completed after delivery
- Apply recency weighting (recent overrides old)
NEVER:
- Skip stage transitions
- Extract low-confidence signals without marking them
- Claim patterns from single occurrences
- Regress stages
- Deliver without marking final stage complete
- Over-interpret neutral language
- signal-patterns.md — extended taxonomy, edge cases
- extraction-techniques.md — regex, heuristics
- sample-analysis.md — complete walkthrough
1---2name: session-analysis3description: This skill should be used when analyzing conversation patterns, identifying frustration or success signals, or when "analyze conversation", "what went wrong", or "patterns" are mentioned.4metadata:5 version: "2.0.0"6---78# Conversation Analysis910Signal extraction → pattern detection → behavioral insights.1112<when_to_use>1314- User requests conversation analysis15- Identifying frustration, success, or workflow patterns16- Extracting user preferences and requirements17- Understanding task evolution and iterations1819NOT for: real-time monitoring, content generation, single message analysis2021</when_to_use>2223<signal_taxonomy>2425| Type | Subtype | Indicators |26|------|---------|------------|27| Success | Explicit Praise | "Perfect!", "Exactly what I needed", exclamation marks |28| Success | Continuation | "Now do the same for...", building on prior work |29| Success | Adoption | User implements suggestion without modification |30| Success | Acceptance | "Looks good", "Ship it", "Merge this" |31| Frustration | Correction | "No, I meant...", "That's wrong", "Do X instead" |32| Frustration | Reversion | User undoes agent changes, "Go back" |33| Frustration | Repetition | Same request 2+ times, escalating specificity |34| Frustration | Explicit | "This isn't working", "Why did you...", accusatory tone |35| Workflow | Sequence | "First...", "Then...", "Finally...", numbered lists |36| Workflow | Transition | "Now that X is done, let's Y", stage changes |37| Workflow | Tool Chain | Recurring tool usage patterns (Read → Edit → Bash) |38| Workflow | Context Switch | Abrupt topic changes, no transition language |39| Request | Prohibition | "Don't use X", "Never do Y", "Avoid Z" |40| Request | Requirement | "Always check...", "Make sure to...", "You must..." |41| Request | Preference | "I prefer...", "It's better to...", comparative language |42| Request | Conditional | "If X then Y", "When A, do B", situational rules |4344Confidence levels:45- High (0.8–1.0): Explicit keywords match taxonomy, no ambiguity, strong context46- Medium (0.5–0.79): Implicit signal, partial context, minor ambiguity47- Low (0.2–0.49): Ambiguous language, weak context, borderline classification4849</signal_taxonomy>5051<stages>5253Load the **maintain-tasks** skill for stage tracking. Stages advance only, never regress.5455| Stage | Trigger | activeForm |56|-------|---------|------------|57| Parse Input | Session start | "Parsing input" |58| Extract Signals | Scope validated | "Extracting signals" |59| Detect Patterns | Signals extracted | "Detecting patterns" |60| Synthesize Report | Patterns detected | "Synthesizing report" |6162Task format:6364```text65- Parse Input { scope description }66- Extract Signals { from N messages }67- Detect Patterns { category focus }68- Synthesize Report { output format }69```7071Edge cases:72- Small scope (<5 messages): Skip Extract Signals, jump to Synthesize73- Re-analysis: Resume at Detect Patterns74- Narrow focus (single signal type): Skip Detect Patterns7576Workflow:77- Start: Create Parse Input `in_progress`78- Transition: Mark current `completed`, add next `in_progress`79- After delivery: Mark Synthesize Report `completed`8081</stages>8283<workflow>84851. Define Scope86 - Message range (all, recent N, date range)87 - Actors (user only, agent only, both)88 - Exclusions (system messages, tool outputs, code blocks)89 - Mark Parse Input `completed`, create Extract Signals `in_progress`90912. Extract Signals92 - Scan messages for signal keywords93 - Match against taxonomy94 - Assign confidence (high/medium/low)95 - Record: type, subtype, message_id, timestamp, quote, context96 - Mark Extract Signals `completed`, create Detect Patterns `in_progress`97983. Detect Patterns99 - Group signals by type/subtype100 - Find clusters (3+ related signals)101 - Identify evolution (signal changes over time)102 - Track repetition (recurring themes)103 - Spot correlations (tool chains, workflows)104 - Mark Detect Patterns `completed`, create Synthesize Report `in_progress`1051064. Output107 - Generate JSON with signals, patterns, summary108 - Include confidence, recommendations, action items109 - Append `△ Caveats` if gaps exist110 - Mark Synthesize Report `completed`111112</workflow>113114<pattern_detection>115116Behavioral patterns from signal clusters:117118| Pattern | Detection | Confidence |119|---------|-----------|------------|120| Repetition | Same signal 3+ times | Strong: 5+ signals |121| Evolution | Signal type changes over time | Moderate: 3-4 signals |122| Preferences | Consistent request signals | Strong: across sessions |123| Tool Chains | Recurring tool sequences (5+ times) | High: frequent use |124| Problem Areas | Clustered frustration signals | Strong: 3+ in same topic |125126Temporal patterns:127- Escalation: Increasing frustration/stronger requirements128- De-escalation: Frustration → success transition129- Cyclical: Same issue recurs across sessions130131</pattern_detection>132133<output_format>134135JSON structure:136137```json138{139 "analysis": {140 "scope": {141 "message_count": N,142 "date_range": "YYYY-MM-DD to YYYY-MM-DD",143 "actors": ["user", "agent"]144 },145 "signals": [146 {147 "type": "success|frustration|workflow|request",148 "subtype": "specific_subtype",149 "message_id": "msg_123",150 "timestamp": "ISO8601",151 "quote": "exact text",152 "confidence": "high|medium|low",153 "context": "brief explanation"154 }155 ],156 "patterns": [157 {158 "pattern_type": "repetition|evolution|preference|tool_chain",159 "category": "success|frustration|workflow|request",160 "description": "pattern summary",161 "occurrences": N,162 "confidence": "strong|moderate|weak",163 "first_seen": "ISO8601",164 "last_seen": "ISO8601",165 "recommendation": "actionable next step"166 }167 ],168 "summary": {169 "total_signals": N,170 "by_type": { "success": N, "frustration": N, ... },171 "key_insights": ["insight 1", "insight 2"],172 "action_items": ["item 1", "item 2"]173 }174 }175}176```177178</output_format>179180<rules>181182ALWAYS:183- Create Parse Input at session start184- Update todos at stage transitions185- Include confidence levels for all signals186- Support patterns with 2+ signals minimum187- Mark Synthesize Report `completed` after delivery188- Apply recency weighting (recent overrides old)189190NEVER:191- Skip stage transitions192- Extract low-confidence signals without marking them193- Claim patterns from single occurrences194- Regress stages195- Deliver without marking final stage complete196- Over-interpret neutral language197198</rules>199200<references>201202- [signal-patterns.md](references/signal-patterns.md) — extended taxonomy, edge cases203- [extraction-techniques.md](references/extraction-techniques.md) — regex, heuristics204- [sample-analysis.md](examples/sample-analysis.md) — complete walkthrough205206</references>