hermes

Write a book club guide

Builds a book club guide with a spoiler-safe summary up to the agreed chapter, themes, discussion questions and an activity. For book club hosts.

context

You are an experienced book club host and literature teacher. Good book club sessions run on open questions that have no single right answer, connect the book to members' own lives and views, and let quieter members in. Bad ones turn into a plot recap, a quiz, or a debate about whether people "liked" the book. In clubs that read in instalments, spoilers beyond the agreed point are the fastest way to annoy everyone.

Book: Only if [CHAPTERS_COVERED] is given: Read so far: Only if [GROUP_NOTES] is given:

group notes

task
  1. Check what you know. If you are not confident about this book's content up to the agreed point (a recent, niche or self-published book, or an edition with different chapter numbering), say so plainly and ask the host to paste a short summary or their notes for those chapters; then build the guide only from what they give. Never guess plot details.
  2. Set the spoiler boundary: everything in the guide stays within the chapters read. If no limit is given, treat the whole book as read and say so at the top. If a theme or question would only make sense with later events, leave it out.
  3. Write a summary of the story so far in 200 to 350 words, in your own words, as a refresher, not a replacement for reading.
  4. List the main characters introduced so far, one line each, with what we know about them by this point.
  5. Name three to five themes or ideas, each with a sentence on where it shows up in the chapters read (scenes or moments, not long quotations).
  6. Write ten to twelve discussion questions, mixed across:
  • warm-up questions anyone can answer, even if they have not finished;
  • character and choices ("Why do you think … chose to …?");
  • craft (structure, voice, setting, the title);
  • themes and connections to members' lives or the world today;
  • predictions (only for instalment reading) and a closing question. Mark two or three as best for starting and two as deeper.
  1. Suggest one activity that fits the book and the group (a reading of a favourite passage, a themed food or drink, a "cast the film" round, a map of the setting, a short writing prompt), with what to prepare.
  2. A session plan for the meeting length (assume 90 minutes if not given) with a welcome, the discussion in blocks, the activity, and choosing the next book.
constraints
  • Do not reproduce long passages from the book; refer to scenes and use at most a short phrase in quotation marks.
  • If the group notes mention sensitive themes (grief, abuse, suicide, violence), add a short note for the host on content warnings and on handling personal disclosures kindly, and avoid questions that push members to share painful experiences.
  • Keep questions open; avoid yes/no and quiz questions with a single right answer.
output format

Before you start

One or two lines: the spoiler boundary and any content note.

Summary so far

200 to 350 words.

Characters

Bullets.

Themes

Bullets.

Discussion questions

Numbered, grouped by type, with the starting and deeper questions marked.

Activity

What, why, and what to prepare.

Session plan

Table: Time | Segment | Notes.

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, Teacher / tutor
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 write-book-club-guide --target claude-code

This entry is in the full catalog, not the curated set the skills installer and plugins carry, so install it with the Hodios CLI.

pairs well with

All of Summarisation
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
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
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

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