business-brainstorm
When you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not…
When you want to read and extract structured notes from a book — PDF, EPUB, MOBI, markdown, .txt, pasted text, or URL to a public-domain work. Reads in chunks (by chapter when a TOC exists, by 50-page blocks otherwise), extracts per-chapter TL;DR + key concepts + quotes + action
$ npx -y skills add coreyhaines31/makerskills --skill read-book --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/read-bookContext preview
The summary Claude sees to decide when to auto-load this skill.
When you want to read and extract structured notes from a book — PDF, EPUB, MOBI, markdown, .txt, pasted text, or URL to a public-domain work. Reads in chunks (by chapter when a TOC exists, by 50-page blocks otherwise), extracts per-chapter TL;DR + key concepts + quotes + action
name: read-book description: When you want to read and extract structured notes from a book — PDF, EPUB, MOBI, markdown, .txt, pasted text, or URL to a public-domain work. Reads in chunks (by chapter when a TOC exists, by 50-page blocks otherwise), extracts per-chapter TL;DR + key concepts + quotes + action items + frameworks, and offers to capture to second-brain raw/ as a highlights- file. Four modes — notes (default, chapter-by-chapter), summary (whole-book TL;DR + 3–5 takeaways), quotes (pull-quote highlights only), study (notes + Q&A spaced-rep prep). Triggers on "/read-book," "read this book," "extract notes from this PDF," "what's in this book," "summarize this ebook," "pull quotes from this." Sibling to watch-video (same content-consumption pattern, different medium). metadata: version: 0.1.1
Sibling to `watch-video`. Same content-consumption pattern: ingest → chunk → extract → optionally capture to second-brain.
Accept:
Detect type from file extension. If ambiguous, ask.
| Invocation | Mode | What you get | |---|---|---| | `/read-book <input>` | **notes** (default) | Chapter-by-chapter: TL;DR + key concepts + quotes + action items + frameworks | | `/read-book <input> summary` | summary | Whole-book TL;DR (1 paragraph) + 3–5 key takeaways + who-it's-for | | `/read-book <input> quotes` | quotes | Pull-quote highlights only, with chapter context and page refs | | `/read-book <input> study` | study | Notes mode + 10–20 spaced-repetition Q&A cards |
If the book is long (>200 pages) and mode is unspecified, default to `notes` but warn it'll take many tool calls.
See `references/sources.md` for per-source ingestion. Output of this step: text content + a chunking plan.
**Chunking strategy** (hybrid, in priority order):
1. **By chapter** if a TOC exists (PDF with bookmarks, EPUB/MOBI converted via pandoc preserves chapter headers)
2. **By page count** for PDFs without TOC: 50 pages per chunk
3. **By character count** for text/markdown: 30,000 chars per chunk (~7,500 words)
Save the chunking plan as `~/Documents/books/<author>-<title-slug>-<YYYY-MM-DD>/chunks.json`:
{
"source": "<path>",
"title": "<book title>",
"author": "<author>",
"type": "pdf",
"total_pages": 287,
"chunking": "by-chapter",
"chunks": [
{"i": 0, "label": "Introduction", "pages": "1-12"},
{"i": 1, "label": "Chapter 1: The Problem", "pages": "13-32"},
...
]
}Loop: 1. Read chunk N (`Read` tool with `pages:` for PDF, full file for text/MD) 2. Extract per the chosen mode (see `references/output-modes.md` for templates) 3. Append the chunk's notes to `~/Documents/books/<workdir>/notes-<NNN>-<label-slug>.md`
For PDFs, **don't read the whole book in one call** — Claude's PDF tool maxes around 10 pages. Process chunks individually.
If a chunk fails to extract anything useful (e.g., it's mostly diagrams or front-matter), log the skip and continue.
Combine all chunk notes into a single `~/Documents/books/<workdir>/notes.md` matching the mode's full-book template (see `references/output-modes.md`).
Top of the file always has the metadata block + the second-brain-compatible frontmatter:
source: <file path or URL> captured: YYYY-MM-DD type: book book_title: <title> author: <author> mode: notes chunks: <count> chunking: <strategy> # <title> by <author> ## TL;DR <2–3 sentences> ## Key takeaways 1. ... ## Chapter notes ... ## Cross-references (suggested for wiki) - Could connect to [[Longevity Biomarkers]] (per Chapter 3 discussion of biomarkers) - Could connect to [[Productivity & Systems]] (per Chapter 7 framework)
The cross-reference suggestions are advisory — they're suggestions for `/sb compile` to act on, not auto-applied. Keep responsibilities separated.
Ask:
> *"Want to capture this to second-brain? I'll write it to `${SECOND_BRAIN_VAULT:-$HOME/Documents/SecondBrain}/raw/highlights-<slug>.md` matching your vault's `highlights-` type prefix."*
Default is **ask**, never auto-write. If yes: 1. Copy the final `notes.md` (with the second-brain-compatible frontmatter at top) to `${SECOND_BRAIN_VAULT:-$HOME/Documents/SecondBrain}/raw/highlights-<slug>.md` 2. Tell the user the path 3. Suggest: *"Run `/sb compile` later to merge this into wiki pages — the cross-reference suggestions in the footer are starting points."*
If the user skips capture, the workdir still has everything — they can grab the file later.
In chat:
| Invocation | Mode | Behavior | |---|---|---| | `/read-book <input>` | notes | Full pipeline, default mode | | `/read-book <input> summary` | summary | Just TL;DR + key takeaways (1 read pass for short books, sampled chapters for long) | | `/read-book <input> quotes` | quotes | Chapter-by-chapter, but on
AI agent skills for the personal operator's craft. Decisions, research, second-brain workflows, content rotation, scenario modeling, CFO cadence, domain hunts, and the meta-skills to author more. Built for founders and indie operators.
When you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not…
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer…
Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management,…
When you have a decision to make and want a structured workflow that picks the load-bearing questions, walks through them,…
When you want multi-source, multi-step research on a topic — competitor research before a sales call, market research for a new…
When you want to brainstorm and check available .com domains for a new project — brand naming, aftermarket pricing (HugeDomains /…