Verified against ChatGPT · 2026-08-11
Summarize a textbook chapter by its actual argument and evidence chain, not a scene-by-scene recap
Produces a chapter summary structured around the author's core claim and the evidence that supports it, distinguishing load-bearing content from illustrative examples so you retain the argument, not just a sequence of facts.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Summarize this chapter for me, but structure the summary around the actual argument the chapter is making, not a beginning-to-end recap of everything that happened in it. CHAPTER TEXT OR DETAILED CONTENTS [Pasted text of a history chapter arguing that railroad expansion, not gold discoveries alone, was the primary driver of westward US settlement patterns] SUBJECT AND COURSE US History survey course, expansion and settlement unit WHAT I'M USING THIS SUMMARY FOR Quick review the night before a midterm covering four chapters, not first-pass learning First, identify the chapter's central claim or thesis in one or two sentences — what is this chapter actually arguing or trying to establish, not just what topic it covers. Then map out the evidence chain: the specific pieces of evidence, examples, or sub-arguments the chapter uses to build toward that central claim, in the logical order they support the argument (which may not be the order they appear in the text, if the chapter builds up to a claim before stating it outright). For each piece of evidence, note in one phrase why it's there — what specifically it's proving or illustrating — rather than just restating what it says. Explicitly separate load-bearing content (an example or piece of evidence the argument would actually fall apart without) from illustrative content (an example that helps understanding but that the argument doesn't structurally depend on) — mark each distinctly, since Quick review the night before a midterm covering four chapters, not first-pass learning probably means I need to prioritize the load-bearing content if I'm short on review time. If the chapter reaches a stated conclusion or implication distinct from its central claim, state that separately at the end. WHAT NOT TO DO Do not produce a paragraph-by-paragraph or section-by-section recap — that reproduces the chapter's structure rather than its argument, which isn't a summary, it's a shortened copy. Do not add outside information or context not present in [Pasted text of a history chapter arguing that railroad expansion, not gold discoveries alone, was the primary driver of westward US settlement patterns]. OUTPUT FORMAT 1. Central claim (1-2 sentences). 2. Evidence chain, each item marked [LOAD-BEARING] or [ILLUSTRATIVE], with a one-phrase note on what it's proving. 3. Stated conclusion/implication, if distinct from the central claim.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
A generic "summarize this chapter" request produces a compressed version of the chapter's own structure — a shorter recap that hits the same points in the same order the text presented them — because that's the lowest-effort form of summarization and matches what GPT-5.1 defaults to without a specific instruction to restructure around argument rather than sequence; the problem is that a sequential recap preserves surface content while discarding the thing a student actually needs to retain, which is the logical chain connecting evidence to claim. Requiring the central claim to be stated first, separate from the summary itself, forces the model to commit to what the chapter is actually arguing before it's allowed to list supporting content, which prevents the common failure where a summary lists five interesting facts from the chapter without ever making clear what they were collectively building toward. Reordering the evidence chain by logical support rather than textual appearance order matters specifically for chapters (common in history, philosophy, and argument-driven science writing) that build up to a thesis rather than stating it in the first paragraph — a sequential summary of such a chapter reproduces the suspense structure of the original writing, which is exactly backward for study purposes, where the student needs the destination stated up front and the evidence organized as support for it. The load-bearing versus illustrative distinction directly serves the stated {{purpose}} — a student reviewing the night before an exam across four chapters needs to know which examples are structurally necessary to explain the argument if asked, versus which ones were included mainly to aid comprehension and can be skipped under time pressure; without this explicit split, all content in a summary reads as equally essential, which is precisely the information a time-constrained review needs but a flat summary doesn't provide.
What you get back
Central claim: The chapter argues that railroad expansion, more than gold rushes, was the primary structural driver of westward settlement patterns in the 1850s-1870s. Evidence chain: [LOAD-BEARING] Settlement density data showing towns clustering along rail lines rather than mining sites after 1869 — this is the chapter's core empirical support, the argument doesn't work without it. [ILLUSTRATIVE] The anecdote about a specific boomtown that emptied after its mine dried up but persisted because of a rail spur — helps make the pattern concrete but the argument doesn't structurally depend on this one case...
Verified against
ChatGPT GPT-5.1 · 2026-08-11
Changelog
- 2026-08-11 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
