okc-bookSummary
Skill0 starsChanged 45 days agoMITView on GitHub
Non-Fiction Book Synthesizer and Curator (/okc-book). Converts books and long documents (PDF, EPUB, DOCX, HTML, RTF, TXT) into rich, actionable, deeply analytical summaries by individual chapters and integrated master notes in Obsidian. Implements the High-Density Actionable Synthesis (HDAS) standard: continuous narrative prose, front-loaded takeaways, explicit mental models, common pitfalls, 15-min action prompts, smart cross-domain commentary, reflection exercises, native Mermaid diagrams, #flashcards, and wiki concept graphs.
In this repository68 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- ai-engineering-chip-huyenSkill
- ask-mattSkill
- book-to-skillSkill
- claude-handoffSkill
- codebase-designSkill
- code-reviewSkill
- daily-noteSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- getContextSizeSkill
- git-guardrails-claude-codeSkill
- graphify-querySkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- improve-codebase-architectureSkill
- knowledge-linkSkill
- knowledge-synthesisSkill
- loop-meSkill
- master-plan-builderSkill
- migrate-to-shoehornSkill
- note-captureSkill
- note-reviewSkill
- notion-curatorSkill
- obsidian-knowledge-curatorSkill
- okc-bookFlashcardsSkill
- okc-diagnosticsAndSynchronizationSkill
- okc-docSkill
- okc-doctorSkill
- okc-driftSkill
- okc-emergeSkill
- okc-exploreSkill
- okc-findSkill
- okc-linterSkill
- okc-normalizeSkill
- okc-setupSkill
- okc-study-multichoiceSkill
- okc-studySkill
- okc-syncSkill
- okc-traceSkill
- okc-urlArticleSkill
- okc-urlPlaylistSkill
- okc-urlPodcastSkill
- okc-urlSpotifySkill
- okc-urlTwitterSkill
- okc-urlYoutubeSkill
- prototypeSkill
- researchSkill
- resolving-merge-conflictsSkill
- scaffold-exercisesSkill
- setup-matt-pocock-skillsSkill
- setup-pre-commitSkill
- setup-ts-deep-modulesSkill
- tddSkill
- teachSkill
- to-specSkill
- to-ticketsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 0 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Default Upload to Obsidian (
VAULT_ROOT): All processed content (master book note, individual chapter notes, images in assets/images/, … - Very specific: line 18
Step 3 (Atomic Batch Commit): Commit all chapter notes, the executive master note, and wiki concepts in a single atomic transaction with …
- Very specific: line 181
Sequential Chapter Generation: Create each Chapter XX — <Title>.md note sequentially in raw/books/<Author> — <Book Title>/ using the …
- Very specific: line 182
Master Note Creation: Create <Author> — <Book Title>.md in the root of raw/books/.
- Very specific: line 183
Wiki Enrichment: Create or update concept pages in wiki/ with bidirectional wikilinks.
- Very specific: line 184
Staging Cleanup: Run uv run python scripts/fetch_book_data.py --clean.
- Very specific: line 185
Vault Sync: Run uv run python scripts/sync_vault.py.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Non-Fiction Book Curator & Synthesizer (okc-bookSummary) — High-Density Actionable Synthesis (HDAS)
Transforms knowledge from non-fiction books and long documents into rich, actionable, and deeply analytical chapter-by-chapter summaries directly inside the Obsidian Vault (VAULT_ROOT), combining continuous narrative depth with active learning, strategic mental models, and immediate real-world application.
🎯 Primary Execution Rules
- Default Upload to Obsidian (
VAULT_ROOT): All processed content (master book note, individual chapter notes, images inassets/images/,#flashcardcards, glossary,wiki/concepts, and Master Plan updates) MUST be written exclusively and by default to the Obsidian Vault (VAULT_ROOT). - Sequential Chapter-by-Chapter Processing (FastMCP Streamlined):
- Step 1 (Fetch & Stage): Execute native FastMCP tool
fetch_book_data(file_path="<file>", slug="<slug>")on theokcserver (or CLI fallbackuv run python scripts/fetch_book_data.py --input <file> --slug <slug>). - Step 2 (Synthesize Chapters & Master Note): Generate chapter notes (
Chapter 00 — <Title>.md,Chapter 01 — <Title>.md, ...), the Executive Master Book Note (<Author> — <Book Title>.md), and relevantwiki/concepts in memory adhering to HDAS standards. - Step 3 (Atomic Batch Commit): Commit all chapter notes, the executive master note, and wiki concepts in a single atomic transaction with incremental sync using FastMCP
commit_curated_batch:commit_curated_batch( raw_notes={ "dataScienceKnowledgeBase/<Category>/raw/books/<Author> — <Book Title>/Chapter 01 — <Title>.md": "...", "dataScienceKnowledgeBase/<Category>/raw/books/<Author> — <Book Title>/Chapter 02 — <Title>.md": "...", }, master_plan_path="dataScienceKnowledgeBase/<Category>/raw/books/<Author> — <Book Title>.md", master_plan_content="...", wiki_notes={"MentalModelName.md": "..."}, target_kb="dataScienceKnowledgeBase/<Category>", fast_sync=True ) - Step 4 (Clean Staging): Execute native FastMCP tool
clean_staging_temp()to safely purgetemp/without terminal commands. - Zero-Spam Policy: Perform any vault checks silently using native cortex tools (
find_by_name,view_file,find_notes). Never run exploratory terminal commands (python3 -c,ls, etc.).
- Step 1 (Fetch & Stage): Execute native FastMCP tool
- High-Density Actionable Synthesis (HDAS Standard):
- Dense Narrative Prose: Articulated explanatory paragraphs explaining cause, effect, and dynamics.
- Front-Loaded Insights: Core mental models named and bolded (e.g.
Insight 1: [Mental Model Name]). - Actionable Tooling (The "How"): Concrete step-by-step implementation, a 15-minute challenge, and a self-reflection prompt per chapter.
- Smart Commentary: Cross-domain synthesis connecting the chapter's thesis to other authoritative works and mental models.
- Common Pitfalls (
[!warning]): Explicit warnings about common misapplications or biases.
- Mandatory Diagrams and Visual Assets:
- Embed extracted images/figures from the source document using
![[assets/images/<slug>-img-X.png]]. - Reconstruct conceptual maps, architectures, and decision workflows using native Mermaid.js diagrams.
- Embed extracted images/figures from the source document using
🎯 File Architecture in Obsidian (VAULT_ROOT)
Each processed book generates the following directory structure inside the Vault:
VAULT_ROOT/dataScienceKnowledgeBase/<Category>/raw/books/
├── <Author> — <Book Title>.md # Executive Master Note (Synopsis, Architecture Map, Index, Flashcards, Glossary)
└── <Author> — <Book Title>/
├── Chapter 00 — <Title>.md # Individual Chapter Note (HDAS Standard)
├── Chapter 01 — <Title>.md
└── ...📋 Standard Chapter Architecture (Chapter XX — <Title>.md)
Each chapter note must contain the following 7 structured sections:
# Chapter XX — <Chapter Title>
> **<Author> — <Book Title>**
> Source: Book / Audio Ingestion · Date: YYYY
> Part of: [[<Author> — <Book Title>]]
> Type: book-chapter
> Processed: DD-MM-YYYY
> Tags: #no-read-yet #book-summary #actionable-insights #mental-models
### 1. Central Thesis & One-Sentence Insight
*The major epiphany of the chapter synthesized with immediate impact.*
Narrative context of how this section integrates into the author's overarching thesis.
### 2. Inquiry Questions
1. Critical question 1...?
2. Critical question 2...?
3. Critical question 3...?
4. Critical question 4...?
5. Critical question 5...?
### 3. Enriched Summary Development (Narrative Depth & Mental Models)
Dense and articulated paragraphs (avoid dry bullet lists) explaining root causes, dynamics, and consequences:
- **Insight 1: [Name of Mental Model / Core Mechanism]**
In-depth explanation of logic, empirical evidence, and historical nuances.
- **Insight 2: [Name of Mental Model / Core Mechanism]**
Operational mechanics and determining factors.
- **Insight 3: [Name of Mental Model / Core Mechanism]**
Strategic implications and industry transformations.
> [!example] Visual Metaphor / Analogy: <Title>
> The author's signature analogy or illustrative story to anchor the concept in memory.
> [!quote] Key Quote & Real-World Case: <Title>
> Real-world case study with its foundational lesson.
> [!warning] Common Pitfall & Bias to Avoid: <Title>
> The typical mistake or trap encountered when erroneously interpreting or applying this principle.
```mermaid
flowchart TD
A[Trigger / Mental Model] --> B[Decision Dynamics]
B --> C[Outcome / Strategic Impact]4. Smart Commentary (Cross-Domain Connections & Extended Context)
High-level analysis connecting the chapter's thesis to other authors, foundational books (e.g., The Second Machine Age, Superintelligence, Homo Deus, Blitzscaling, Lean Startup), or contemporary technological developments.
5. Practical Application Guide (The "How")
- Actionable Step-by-Step: 3 to 4 specific steps to implement the concept at work, in engineering projects, or in decision-making.
- Immediate 15-Minute Challenge: Practical hands-on exercise to execute today.
- Self-Reflection Prompt: Introspective inquiry to audit your current workflow or architecture.
6. Critical Analysis & Model Boundaries
Honest evaluation of author biases, edge-case exceptions where the model fails, and counterarguments from the field.
7. Executive One-Sentence Takeaway
The definitive actionable conclusion to remember always.
---
## 📖 Executive Master Note Structure (`<Author> — <Book Title>.md`)
The Master Note serves as the central hub for the book at the root of `raw/books/`:
```markdown
# <Book Title>
> **<Author> — <Book Title>**
> Type: book | non-fiction
> Processed: DD-MM-YYYY
> Status: [[Chapter 00 — <Title>]], [[Chapter 01 — <Title>]] ...
> Tags: #no-read-yet #book-summary #master-note
## 📌 Executive Synopsis
(Fluid summary of 300-500 words covering the core thesis of the book, the problems it addresses, and the value of reading it).
## 🗺️ Book Architecture Map
```mermaid
mindmap
root((<Book Title>))
Part 1: Foundations
[[Chapter 00 — <Title>]]
[[Chapter 01 — <Title>]]
Part 2: Mechanics and Dynamics
[[Chapter 02 — <Title>]]📚 Chapter Index & Mental Models
| Chapter | Title | Mental Models & Key Concepts | Link |
| Ch. 00 | <Title> | [[ConceptA]], [[ConceptB]] | [[Chapter 00 — <Title>]] |
| Ch. 01 | <Title> | [[ConceptC]] | [[Chapter 01 — <Title>]] |
🎴 Study Flashcards (#flashcard)
#flashcard Q: What is the central thesis advocated by the author in the book? A: Concise and precise answer.
Q: How does concept X connect to principle Y? A: Dynamics explanation.
📖 Specialized Glossary
Term: Detailed definition in the context of the book.
🔗 Related Wiki Concepts
- [[ConceptA]]
- [[ConceptB]]
---
## 🚀 Execution & Integration Workflow
1. **Ingest and Segment**: Begin with `uv run python scripts/fetch_book_data.py --input <file> --slug <slug>`.
2. **Sequential Chapter Generation**: Create each `Chapter XX — <Title>.md` note sequentially in `raw/books/<Author> — <Book Title>/` using the 7-section HDAS standard.
3. **Master Note Creation**: Create `<Author> — <Book Title>.md` in the root of `raw/books/`.
4. **Wiki Enrichment**: Create or update concept pages in `wiki/` with bidirectional wikilinks.
5. **Staging Cleanup**: Run `uv run python scripts/fetch_book_data.py --clean`.
6. **Vault Sync**: Run `uv run python scripts/sync_vault.py`.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.

