
Book Study
Structure book notes into linked concept, case, model, and chapter wiki pages for a personal knowledge base your agent can extend.
Overview
Book-study is a journey-wide agent skill that turns reading into linked wiki pages (concepts, cases, models, chapters)—usable whenever a solo builder needs to capture and reuse book knowledge before committing to product
Install
npx skills add https://github.com/sanyuan0704/code-review-expert --skill book-studyWhat is this skill?
- Four page archetypes: concepts, cases, models, and chapter summaries with consistent sections
- Wiki-style cross-links between same-book and cross-book related entries
- Separation of book voice (What the Book Says) vs personal restatement (My Understanding)
- Source citations with chapter and page references on every template
- Credibility and limitations blocks on case and model pages for honest synthesis
- 4 page archetypes: concepts, cases, models, and chapter summaries
Adoption & trust: 1 installs on skills.sh; 3.6k GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You finish books with highlights and loose notes but no consistent structure to link ideas, cases, and models across titles.
Who is it for?
Solo builders maintaining a personal or repo-local book wiki with concepts, cases, and frameworks linked for later research and planning.
Skip if: Teams that only need one-off summaries without wiki linking, or workflows that require automated book ingestion or copyright-heavy full-text copying.
When should I use this skill?
Starting or extending a book wiki in markdown and you need consistent page templates with sourcing and cross-links.
What do I get? / Deliverables
You get repeatable markdown templates with cross-links and sources so agents can add pages that form a searchable book wiki.
- Concept wiki page
- Case or model wiki page
- Chapter summary page with linked knowledge points
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Capture competitor and market insight books as concept and case pages before choosing a niche.
Document pricing and positioning frameworks from a business book as model pages with limitations.
Add architecture-adjacent book models to your repo docs with Sources and Related links.
Turn chapter summaries into citable outlines for blog posts without losing page references.
Update case pages when real-world experiments confirm or contradict a book’s claims.
How it compares
Use structured wiki templates instead of unstructured reading notes or generic summarize-this-chapter prompts.
Common Questions / FAQ
Who is book-study for?
Solo and indie builders who read non-fiction or technical books and want durable, agent-friendly PKM pages in markdown with explicit sourcing.
When should I use book-study?
During Idea research when capturing competitor or market books, during Validate when grounding scope in cited frameworks, during Build docs when documenting domain models, and during Grow content when turning book insights into explainers.
Is book-study safe to install?
It is documentation templates only with no shell or network behavior implied by the skill text; review the Security Audits panel on this Prism page before installing from any third-party skill pack.
SKILL.md
READMESKILL.md - Book Study
# Book Wiki Page Templates ## Concept Page (concepts/) ```markdown # Concept Name > One-line definition (in your own words) ## What the Book Says (Original explanation, preserve key phrasing) ## My Understanding (Restate in plain language — the simpler the better) ## Key Evidence - Case/Experiment A → [[cases/xxx]] - Data point B ## Real-World Application (How to use this concept in daily life/work) ## Related - Same book: [[concepts/related-concept]] - Cross-book: [[/cross-book/concepts/related-concept]] ## Sources - <Book Title> Chapter X, P.xxx ``` ## Case Page (cases/) ```markdown # Case Title > One-line summary ## Description (Concise retelling) ## What It Proves (Which concept/model does this case support) ## Credibility (Reproducible? Sample size? Controversial?) ## Related - [[concepts/related-concept]] - [[models/related-model]] ## Sources - <Book Title> Chapter X, P.xxx ``` ## Model Page (models/) ```markdown # Model/Framework Name > One-line summary of what problem this model solves ## Structure (Steps, elements, flow) ## When to Use (Applicable scenarios) ## Limitations (When it doesn't apply) ## Relationship to Other Models - Complementary: [[models/xxx]] - Alternative: [[models/yyy]] ## Sources - <Book Title> Chapter X, P.xxx ``` ## Chapter Summary (chapters/) ```markdown # Chapter X: Chapter Title > One-line summary of the core argument ## Core Argument (What this chapter is really saying) ## Knowledge Points - [[concepts/concept-a]] - [[models/model-b]] - [[cases/case-c]] ## Relationship to Adjacent Chapters (What it builds on, what it leads to) ## My Takeaway (Biggest insight from this chapter) ``` ## Question Page (questions/) ```markdown # Question Description - **Origin**: Raised while reading Chapter X - **Type**: Doubt / Extended Thinking / Conflicts with Existing Knowledge - **Status**: Open / Resolved ## My Thinking (Current understanding or hypothesis) ## Possible Answers (Fill in if later chapters provide answers) ## Related - [[concepts/related-concept]] ``` ## Quote Page (quotes/) ```markdown # Quote Excerpt > "Original quote text" - **Source**: <Book Title> Chapter X, P.xxx - **Context**: What the author was discussing when they said this - **Why It Resonates**: (user fills in) - **Related**: [[concepts/related-concept]] ``` ## Cross-Book Concept Page (cross-book/concepts/) ```markdown # Concept Name > Synthesized definition from multiple books ## Perspectives by Book - <Book A>: focus/definition → [[book-a/concepts/xxx]] - <Book B>: focus/definition → [[book-b/concepts/xxx]] ## Synthesized Understanding (Most complete understanding after reading multiple books) ## Consensus and Disagreements (Where authors agree, where they diverge) ``` # Pedagogy Reference — Socratic Mastery Learning for Reading ## Core Principle: Bloom's 2-Sigma One-on-one tutoring with mastery learning produces 2 standard deviations of improvement over conventional instruction. The two key ingredients: 1. **Mastery learning**: Don't advance until the current unit is truly understood 2. **1-on-1 tutoring**: Adapt pace, style, and content to the individual learner For book study specifically: "truly understood" means the reader can explain the idea in their own words, give a novel example, and apply it to their own problem — not just recall what the author wrote. ## Socratic Questioning Techniques Never lecture. Instead: - Ask questions that lead the learner to discover the answer - When they're stuck, don't explain — ask a simpler question - When they answer correctly, don't just confirm — ask them to explain why ### Question Types | Type | Purpose | Example | |------|---------|---------| | Clarification | Test understanding depth | "Can you explain that in different words?" | | Assumption probe | Surface hidden beliefs | "What are you assuming when you say that?" | | Evidence request | Connect to support | "What evidence from the book supports that?" | | Counter-example