book-summarizer
Skill12 starsChanged 5 months agoMITView on GitHub
Distills a book into a clear, faithful summary at the depth the reader wants — from a one-paragraph gist to chapter-by-chapter notes — surfacing the core thesis, key ideas, memorable examples, and actionable takeaways without distortion. Use this skill when a user asks to "summarize this book", "give me the key takeaways from X", "what's the main idea of X", "TL;DR of X", "chapter summary", or wants the actionable points or a book-club discussion guide.
Files
Book Summarizer
Overview
This skill produces a faithful, well-structured summary of a book at the requested depth — a one-line gist, an executive summary, key takeaways, or chapter-by-chapter notes — capturing the central thesis, the supporting ideas, the most memorable examples, and what the reader can actually do with it.
Keywords: book summary, key takeaways, TL;DR, main idea, chapter summary, executive summary, book notes, book club, nonfiction, study notes.
When to use vs. not
Use this to summarize, extract takeaways from, or build study/discussion notes for a book the reader names or provides. Accuracy first: if you don't actually know a book's content, say so rather than inventing — never fabricate quotes, statistics, or plot points. For very recent or obscure titles, ask the user to paste text or confirm details. Note that a summary is no substitute for reading when nuance matters (e.g., for academic citation).
Inputs to gather first
- The book (title + author — confirm you have the right one).
- Depth wanted — one-liner, ~1 page, key takeaways, or chapter-by-chapter.
- Purpose — decide whether to read it, apply it, prep a discussion, study for an exam, or recall it.
- Fiction or nonfiction (changes the structure — themes/plot vs. thesis/arguments).
- Spoiler tolerance for fiction.
Workflow
- Confirm the book and your confidence. State the title/author and that you can summarize it accurately. If unsure, ask for text or flag the uncertainty up front.
- Identify the spine. For nonfiction: the central thesis and the 3–7 big ideas that support it. For fiction: premise, central conflict, themes, and arc (respecting spoiler preference). See
references/summary-structures.md. - Summarize at the requested depth:
- One-liner: the single core message in a sentence.
- Executive (~1 page): thesis + key ideas + why it matters.
- Takeaways: a ranked, actionable bullet list.
- Chapter-by-chapter: 2–4 lines per chapter capturing each one's point.
- Keep the best evidence. Preserve the one or two examples, studies, or scenes that make each idea stick — concrete beats abstract.
- Add actionable takeaways (for nonfiction): what to do differently, as concrete steps.
- Stay faithful + neutral. Represent the author's argument accurately before adding any critique. Separate "what the book says" from "my take." Flag where the book is contested if relevant.
- (Optional) discussion/study layer. Book-club questions, key terms, or quiz prompts on request.
Decision framework
| Reader wants to… | Deliver |
| Decide whether to read it | One-liner + 3 takeaways + who it's for |
| Apply the ideas | Key takeaways as concrete actions |
| Recall a book they read | Executive summary + memorable examples |
| Study / cite | Chapter-by-chapter + key terms (+ caveat to verify in source) |
| Run a book club | Themes + 5–8 discussion questions |
Worked example
See examples/atomic-habits.md for layered summaries (one-liner → takeaways → structure) of a well-known nonfiction title.
Best Practices
- Lead with the core message — the reader should get the thesis in the first sentence.
- Faithful before critical — represent the argument accurately, then optionally evaluate.
- Keep concrete examples — they're what makes ideas memorable.
- Make nonfiction actionable — turn ideas into steps.
- Match depth to purpose — don't give chapter notes to someone who wants a TL;DR.
- Flag uncertainty rather than inventing.
Common Pitfalls
- Fabricating quotes, data, or plot when the book isn't actually known — always avoid.
- Listing chapters without extracting each chapter's point.
- Injecting opinion as if it were the author's.
- Losing the thesis in a pile of details.
- Spoiling fiction without asking.
- Over-summarizing to the point the nuance that matters is gone — note when reading the source is necessary.
Other versions3 projects use a version of this.
Word for word · 2
- jaskirat1616/grok-skills★ 22100% same
- JayRHa/AgentSkills★ 12100% same
Edited · 0
None found.
Wrote their own version · 1
- anarefin/ai-agent-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository75 other files it gives its agents.
- 0-templateSkill
- ab-test-analyzerSkill
- adr-authorSkill
- api-designerSkill
- api-docs-writerSkill
- aws-cost-optimizerSkill
- bash-script-hardeningSkill
- blog-post-writerSkill
- changelog-keeperSkill
- chart-chooserSkill
- code-reviewerSkill
- competitive-analysisSkill
- concept-explainerSkill
- cover-letter-writerSkill
- cron-schedulerSkill
- data-pipeline-architectSkill
- debug-detectiveSkill
- decision-matrixSkill
- dependency-upgraderSkill
- dockerfile-proSkill
- email-composerSkill
- error-handling-patternsSkill
- event-plannerSkill
- flashcard-generatorSkill
- gdpr-data-mapperSkill
- gift-advisorSkill
- github-actions-builderSkill
- git-workflowSkill
- habit-builderSkill
- incident-postmortemSkill
- interview-prepSkill
- job-description-writerSkill
- json-schema-authorSkill
- kubernetes-manifest-authorSkill
- language-tutorSkill
- meal-plan-builderSkill
- meeting-summarizerSkill
- mermaid-diagram-builderSkill
- nginx-config-proSkill
- observability-setupSkill
- okr-writerSkill
- pandas-data-cleaningSkill
- people-dataSkill
- performance-profilerSkill
- personal-budget-plannerSkill
- presentation-builderSkill
- project-plannerSkill
- prompt-engineerSkill
- proofreaderSkill
- public-speaking-coachSkill
- rag-pipeline-designerSkill
- readme-generatorSkill
- refactoring-guideSkill
- regex-architectSkill
- release-notes-writerSkill
- resume-writerSkill
- salary-negotiatorSkill
- secrets-managerSkill
- secure-code-reviewSkill
- secure-password-policySkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

