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.
The reader wants to understand what a book argues, how well it argues it, and what to do with it, not a chapter-by-chapter recap. The biggest risk is a confident summary of a book you do not actually know well: invented chapters, quotes or studies are worse than no summary.
Only if [PURPOSE] is given:
- Decide what you are working from. If the input is the user's notes or text, summarise only that and say so. If it is a title, judge honestly how well you know the book. If you do not recognise it, or know only its reputation, say so, offer what you can say with confidence, and ask the user to paste notes or a table of contents. Do not produce the full summary from guesses.
- State the thesis in one or two sentences: the claim the author wants the reader to accept.
- Lay out the core argument as a short chain: the problem, the author's diagnosis, the proposed answer, and why the author thinks it works.
- Explain five to eight key ideas, each in plain words with an example of how it shows up in real life.
- Describe the evidence the author relies on (research, case studies, personal experience, history) and how strong it is.
- Give the main critiques and limits: where findings have not held up, where the argument overreaches, and who the advice fits less well. Attribute criticism to its general source ("later replication attempts", "reviewers in the field") rather than inventing names.
- Turn it into three to five concrete actions for the user's purpose, or for a general reader if no purpose is given.
- Say who should read it in full and which chapters, if you know them, give the most value.
- No direct quotes unless they appear in the user's own notes. Paraphrase instead.
- Do not invent chapter titles, page numbers, studies, statistics or anecdotes. If unsure of a detail, leave it out or mark it "(verify)".
- Separate what the author claims from what is well established.
- For fiction, adapt: replace argument and evidence with premise, themes, characters and craft, and avoid spoilers unless the user asks.
- Aim for a summary readable in five minutes.
- Separate what you verified from what you inferred. Mark inferences as such.
- When you do not know, say "I don't know" once and state what would settle it.
Start with one line: "Working from: your notes" or "Working from: my general knowledge of the book (confidence: high, medium or low)".
In one paragraph
The core argument
A numbered chain of three to five steps.
Key ideas
Numbered: idea in bold, then two or three sentences and an example.
Evidence
Critiques and limits
Apply it
Checklist of three to five actions tied to the purpose.
Read it in full if
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
- made for
- Anyone, personal use, Student, People manager, Founder / business owner
- 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
use in
npx @hermes-hq/hodios install summarize-book --target claude-codenpx skills add hermes-hq/hodios-dist --skill summarize-book -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-productivity@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of SummarisationMake reading notes
Turns highlights from an article or book into atomic, linkable notes written as claims in plain words, with source references, link suggestions and prompts for the reader's own takeaways.
make-reading-notesBuild 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-digestCompare 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-documentsExtract 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-deadlinesSummarise 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-threadSummarise 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