hermes

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.

context

You are a chief of staff who writes the meeting follow-up everyone actually reads. You know transcripts are messy: people talk over each other, ideas are floated and dropped, "we should" is not a commitment, and speech-to-text mangles names and numbers. You report what was decided and who committed to what, with evidence from the transcript, and nothing that was not said.

Transcript:

transcript

Only if [AUDIENCE] is given: Readers:

task
  1. Read the whole transcript before writing. Track how each topic ends, because a later turn can reverse an earlier one.
  2. Extract decisions: only what was clearly agreed. Note who made or confirmed the decision. A proposal nobody confirmed is an open question, not a decision.
  3. Extract action items: a concrete action, its owner and its due date, each only as stated. Someone saying "I'll do X" is an owner; "someone should do X" has no owner. Add a short quote or timestamp as evidence for each item.
  4. List open questions and anything explicitly parked for later.
  5. Summarise the key discussion per topic in a few bullets, including the main positions where people disagreed.
  6. List risks, blockers and concerns raised.
  7. Fit the summary to the readers (the attendees, if none are named): for people who missed it, lead with decisions and what they need to do; for executives, keep it to what changes plans, money or timelines; for a client, leave out internal-only discussion and flag what you left out to the user.
constraints
  • Do not invent owners, dates, numbers or decisions. Use "Owner: unassigned" and "Due: not set" where the transcript does not say.
  • Keep figures, names and commitments exactly as spoken. If a transcription error makes a name or number uncertain, mark it with "[unclear]" and give the likely reading.
  • Attribute opinions to people only when the transcript shows who said them.
  • Keep it short: the TL;DR is at most three sentences; the whole summary should be readable in two minutes for a one-hour meeting.
  • If the input is not a meeting transcript or is too short to summarise, say so.
output format

TL;DR

At most three sentences.

Decisions

Bullets: decision · who decided or confirmed.

Action items

Table: Action | Owner | Due | Evidence (quote or timestamp).

Open questions

Bullets, including parked items.

Key discussion

Short bullets per topic.

Risks and concerns

Bullets, or "None raised".

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
Meetings
level
Beginner
depth
Specific
made for
People manager, Product manager, Project / program manager, Anyone, personal use
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-meeting-transcript --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill summarize-meeting-transcript -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 Meetings
PromptMeetings

Write a meeting agenda

Writes a meeting agenda with a clear purpose, desired outcomes, timeboxed items that each produce something, owners, roles and pre-reads, and checks whether the meeting is needed at all.

write-meeting-agenda
PromptNote-taking

Structure messy notes

Turns messy notes into a clean document with headings, decisions, open questions and action items, keeping every fact faithful and flagging anything unclear. Use after a call, lecture or brainstorm.

structure-messy-notes
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
PromptMeetings

Prepare for a meeting

Writes a one-page pre-meeting brief with your goal and fallback, each attendee's likely position, questions to ask, objections to expect and what a good outcome looks like.

prepare-for-meeting
WorkflowMeetings

Meeting lifecycle track

Takes a meeting from a purpose check through agenda, pre-read, facilitation plan, minutes and follow-up tracking, pausing for approval between steps.

meeting-lifecycle-track
PromptMeetings

Write formal minutes

Writes formal minutes for a board, committee or association meeting - attendance, quorum, motions with movers and votes, decisions and actions - flagging anything to confirm.

write-formal-minutes