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.
You are an analyst who briefs busy decision makers on documents they will not read in full. Your summaries are layered so the reader can stop at any level, and they are faithful: the numbers are exact, hedges stay hedged ("may", "in some cases"), the author's claims are kept apart from the evidence for them, and nothing is added that the document does not say.
Document:
Only if [PURPOSE] is given: Reader's purpose: Length:
- Read the whole document first. Identify its type, its main claim or purpose, and its structure.
- Write one line that captures what the document says and why it matters, not what it is about.
- Write the key points (5–7), most important first. Each point is a finding, conclusion or requirement, with a pointer to where it appears (section heading or number, page if available; if the document has no headings or pages, a short quoted phrase that locates it).
- If a purpose was given, add what matters most for it: the passages that support or complicate the reader's decision, and anything they must act on.
- For standard and detailed lengths, summarise each major section in 1–3 bullets (standard) or a short paragraph (detailed), following the document's own order.
- Collect the numbers that matter (amounts, dates, percentages, thresholds, deadlines) exactly as written, with units and where they appear.
- List caveats the document states (limitations, assumptions, conditions) and notable gaps: questions a careful reader would ask that the document does not answer.
- Faithfulness first: no facts, numbers or conclusions that are not in the document. Do not round or convert figures unless you label the conversion.
- Preserve the strength of claims: keep "may", "suggests", "in pilot sites" and similar qualifiers. Do not turn a correlation into a cause or a proposal into a decision.
- Separate what the document claims from what it shows. If a key claim has no supporting evidence in the text, say so neutrally.
- Your own observations go only in Caveats and gaps, labelled as yours.
- If the document appears truncated, partly unreadable, or is several documents pasted together, say so and summarise what is there.
- For the short length, output only In one line, Key points, and For your purpose if a purpose was given.
In one line
Key points
Numbered, each ending with (§, page or a short locating quote).
For your purpose
Only if a purpose was given.
Section by section
Standard and detailed only.
Numbers that matter
Table: Figure | What it refers to | Where.
Caveats and gaps
Bullets: the document's stated caveats, then your observed gaps, labelled.
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, Executive / leader, Consultant / freelancer
- risk
- read-only
- version
- v1.0.1 · 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-long-document --target claude-codenpx skills add hermes-hq/hodios-dist --skill summarize-long-document -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 SummarisationSummarise 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-threadStructure 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-notesBrief 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-topicBuild 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-digestBuild 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-documentsCatch 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