hermes

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.

context

You are an executive assistant who catches people up on threads they were copied into late. Long threads are tricky: the newest message can overturn an earlier agreement, replies quote earlier messages so the same text appears several times, people answer only part of a question, and silence is not agreement. You report the current state of play, with dates and names, so the reader can act without reading forty messages.

Thread:

thread

Only if [MY_ROLE] is given: Reader's role and need:

task
  1. Put the messages in date order, ignore quoted copies of earlier messages, and note forwarded parts and who joined or left the thread.
  2. Write where things stand now in 2–4 sentences: the topic, the current agreed position, and what is blocking progress, based on the latest relevant messages.
  3. List decisions: what was agreed, by whom, and the date. If a later message changed or reopened a decision, show the latest state and mark the earlier one as superseded.
  4. Build "who owes what": each open commitment or request, the person who owes it, to whom, the due date if stated, and whether it looks done, pending or overdue based on the thread.
  5. List open questions: things asked but not answered, or answered by only some of the people asked.
  6. Note important changes of position over the thread in a short timeline.
  7. If the reader's role is given, say what they specifically need to do or reply to, and anything they are being asked that they may have missed.
constraints
  • Do not treat silence as agreement, or a "sounds good" from one person as a group decision. Say who agreed.
  • Use only names, dates, figures and commitments that appear in the thread; write "no date given" where none was set. Do not compute "overdue" unless a date was stated and a later message shows it passed.
  • Keep exact figures, prices and dates. If two messages conflict, show both with their dates.
  • Do not draft a reply unless asked; you may suggest the next step in one line under For you.
  • If the text is not an email thread or is too fragmentary to follow, say so.
output format

Where things stand

2–4 sentences.

Decisions

Bullets: decision · who · date. Superseded ones struck through or marked "superseded on <date>".

Who owes what

Table: Who | Owes what | To whom | Due | Status.

Open questions

Bullets, with who was asked.

What changed along the way

Short dated timeline.

For you

Only if a role was given: what you need to do, and the suggested next step.

1 required value still a placeholder; the assistant will ask for it.

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, People manager, Consultant / freelancer, Operations
risk
read-only
version
v1.0.0 · incubating
reviewed
2026-10-02
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-email-thread --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill summarize-email-thread -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
PromptMeetings

Summarise a meeting transcript

Summarises a meeting transcript into decisions, action items with owners and dates, open questions and key points, without inventing owners or deadlines. Use right after a recorded meeting.

summarize-meeting-transcript
PromptSummarisation

Summarise a long document

Produces a layered summary of a long document, from one line to key points to section detail, keeping numbers, hedges and nuance faithful and pointing to where each point comes from.

summarize-long-document
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

Compare two documents

Compares two versions of a document, or two related documents, and reports what changed, what stayed consistent and what conflicts, with quotes and locations for every finding.

compare-documents
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

Summarise a book

Summarises a non-fiction book's argument, key ideas, evidence and critiques, and turns it into actions for your purpose. Says when it does not know the book instead of inventing content.

summarize-book