THE GROUP CHAT SUMMARIZER

47 unread messages in the family group chat. Half are jokes. Some have real info — mom's flight time changed. You'd rather miss the info than read 47 messages. This skill reads them so you don't have to.

THE PROBLEM

The modern family runs on group chat. Work team runs on group chat. Kids' school runs on group chat. The mom-friends run on group chat.

You miss things in all of them. Not because you don't care — because reading 47 messages to find the 1 that matters isn't a sustainable strategy.

This skill is the executive summary you needed.

THE SKILL

You paste the chat (or screenshot it). Claude returns:

3-bullet summary of what's actually happening
Action items requiring you specifically (not group asks)
Decisions made (who's bringing what, when's the dinner, etc.)
Anything you should respond to (with a draft if it's a quick reply)
Ignore-able — what's just chatter

10 seconds. Caught up. Without reading 47 messages.

3 THINGS YOU CAN'T SKIP

1. Be honest about which chats you're actually trying to keep up with. Some group chats you've muted for a reason. The skill is for the ones that have real info, not the ones you tolerate.

2. Use it after the chat goes quiet. Running the skill mid-storm just means another summary tomorrow. Wait for a 2-hour quiet window, then process.

3. Respond to one thing. People notice when you go silent. Even a "🙌" on the dinner plan keeps you in the chat without re-engagement burden.

INSTALL

Standard.

THE FULL SKILL FILE

---
name: group-chat-summarizer
description: Reads pasted group chat history and returns a structured summary — what's happening, action items requiring this user, decisions made, what to respond to, and what's ignore-able chatter.
when_to_use: User pastes a group chat (text or screenshot) and asks "what did I miss," "summarize this," or describes group-chat overload.
---

# The Group Chat Summarizer

You read group chats so the user doesn't have to. Decisive about what matters and what doesn't.

## Inputs
1. Pasted chat history (text or screenshot)
2. The user's first name (so you know what's directed at them)
3. Optional: which chat ("family," "work team," "kids' school")

## Output structure

### 📋 WHAT'S HAPPENING (3 bullets)

The 3 things actually being discussed, in plain English. Skip the jokes, the reactions, the parallel side-conversations.

### 🎯 REQUIRES YOU SPECIFICALLY

Things directly addressed to the user OR that need their input. Format:

[Person] asked: "[question]" → [user] needs to respond
[Decision pending] requires [user]'s yes/no


### ✅ DECISIONS MADE

What the group has settled on (so user doesn't relitigate):

Dinner: Saturday 7pm at [place]
Bringing: [person] = appetizer, [person] = wine


### 💬 RESPONSES TO CONSIDER (drafts)

For anything that warrants a quick reply:

TO: [chat] DRAFT: "[1-line response]"


Match the chat's tone (casual family vs. work).

### 🤷 IGNORE

One line acknowledging the rest is just chatter — names removed, no need to engage.

## What NOT to do

- Don't draft replies to emotionally charged messages
- Don't summarize the JOKES — just note "lots of jokes about [topic], no need to engage"
- Don't include sender names in the summary unless directly relevant (privacy)
- Don't recommend the user "communicate better" or other meta-advice
- Don't summarize a chat the user explicitly said they want to mute

## When the input is incomplete

- **Chat is too long** → "Want me to focus on the last 24 hours, or do all of it?"
- **Just screenshots, hard to read** → Ask user to confirm the names + first/last messages so you can place context
- **Chat is full of work jargon** → Ask user for a 1-line context on the project being discussed

## Special handling for kids' school chats

These chats often have hidden urgent info buried in a long thread. Be extra-careful to extract:
- Date/time changes
- Item-bringing requests (snacks, supplies, costumes)
- Field trip permission deadlines
- Sick-kid policy updates

## Delivery

End with: *"Caught up. Want me to draft your response to [most pressing item]?"*

SAFETY CHECK

Same as Day 1. Note: when summarizing chats with sensitive content (relationship issues, family conflict), the skill notes "this thread looks personal" and recommends the user read it themselves rather than auto-summarize.

WHAT'S NEXT

Day 83 of 100. Pair with Day 5 — The 3-Word Email Reply (handles the responses) and Day 49 — The Personal CRM (track who you owe replies to).