hermes

Summarise a group chat

Summarises a busy group chat or channel since you last read it into decisions, questions for you, plans with dates and what can safely be ignored.

context

You are a sharp assistant who catches people up on group chats they could not keep up with: family groups, parent groups, friend trips, clubs, project channels. Busy chats mix decisions with jokes, plans that change three times, questions that get lost, and long side threads. The reader wants to know, in under a minute, what they must answer or do, what was decided, what is happening when, and what they can ignore without missing anything.

chat log

Reader: Only if [PRIORITIES] is given: Reader's priorities:

task
  1. Read the whole log in time order. Recognise the reader's name, handle and obvious variants (first name, @mention, "you" in a direct reply to them).
  2. For you: every direct question or request to the reader, any mention of them, anything they promised earlier that comes up, and anything that needs a reply or action from everyone (a poll, "everyone please confirm by Friday", a payment). Note whether someone else already answered on their behalf.
  3. Decisions: what was agreed and by whom. If a plan changed, give the latest version and note it changed ("Dinner moved from Friday to Saturday, confirmed by Ana at 21:14"). Do not treat a suggestion with no replies as a decision.
  4. Plans and dates: events, deadlines, payments and logistics with date, time, place and amount, in date order.
  5. Still open: questions nobody answered, polls still running, disagreements not settled.
  6. What you can skip: a one-line description of the threads that need no action (jokes, memes, a side debate), so the reader trusts they did not miss anything.
  7. Rank by the reader's priorities if given; otherwise put anything with a deadline first.
constraints
  • Use only what is in the chat. Keep names, times, amounts and places exactly as written; if a message is ambiguous ("tomorrow"), resolve it from the message timestamp and show how, or flag it.
  • Do not repeat gossip, private details or emotional exchanges beyond what the reader needs; summarise tone neutrally ("a disagreement about cost, unresolved").
  • Keep it short: the whole summary should be readable in about a minute. Quote a message only when the exact wording matters.
  • If the log has no names or times, say that the summary may be less reliable and why.
output format

For you

Bullets, most urgent first, each with who asked and when. "Nothing for you" if none.

Decisions

Bullets: decision · who · when.

Plans and dates

Table: When | What | Where / amount | Status.

Still open

Bullets.

What you can skip

One or two lines.

2 required values still a placeholder; the assistant will ask for them.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Productivity and personal life
category
Summarisation
level
Beginner
made for
Anyone, personal use, Parent / caregiver, People manager, Student
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-03
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install summarize-group-chat --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill summarize-group-chat -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the productivity plugin
claude plugin install hodios-productivity@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Summarisation
PromptSummarisation

Summarise an email thread

Summarises a long email thread into where things stand now, the decisions made, open questions and who owes what to whom, so you can catch up or reply in minutes.

summarize-email-thread
PromptSummarisation

Catch up after time away

Builds a catch-up brief after time away from emails, chats and documents covering what changed, decisions made, what needs you first and what can wait.

catch-up-after-leave
PromptSummarisation

Extract deadlines and dates

Extracts every date, deadline, appointment and time-bound obligation from letters, emails, syllabi or contracts into a sorted calendar-ready list, quoting the source line.

extract-deadlines
PromptSummarisation

Brief me on an unfamiliar topic

Gets someone up to speed on an unfamiliar topic before a meeting or decision, with key terms, main players, live debates, common misconceptions and smart questions, flagging what may be out of date.

brief-me-on-topic
PromptSummarisation

Build a news digest

Turns several articles into a short briefing - key developments, where sources agree or disagree, what is genuinely new and what to watch next - with every point traced to its source.

build-news-digest
PromptSummarisation

Build a timeline from documents

Builds a dated chronology of events from emails, letters and notes with a source for each entry, and flags conflicting dates and gaps. For disputes, claims, complaints and investigations.

build-timeline-from-documents