Imported from BlackFast/bolan-skill (SKILL.md). Install upstream with npx skills add BlackFast/bolan-skill. Copyright stays with the author.

name: bolan description: Bolan, meaning 博览群书, turns a book, manuscript, excerpt, PDF, EPUB, DOCX, TXT, Markdown file, notes, pasted text, or a multi-book reading list into a distilled conversational persona. It supports single-book personas and evolving bookshelf souls: a categorized, versioned spirit distilled from several related books that can keep absorbing similar books over time. It uses internal text validation and external reception validation from sources such as Douban, Amazon, Goodreads, professional reviews, academic/industry discussion, and reader criticism. Use when the user asks natural book-reading prompts such as “蒸馏这本书《》”, “蒸馏这几本书”, “蒸馏这个书单”, “把这些书合成一个灵魂”, “我要跟这本书《》聊天”, “我要跟这组书的灵魂聊天”, “把《》加入某某之魂”, “这本书《》说了啥”, “这本书怎么想”, “这个书群怎么看”, “帮我读《》”, “拆解《》”, or after a book or bookshelf soul is distilled wants to keep asking it what it thinks, how it would answer, how it would challenge the reader, or how its logic applies to a concrete question.

Bolan · 博览群书

Bolan 把书处理成可对话的思想人格。单书模式把一本书处理成“书本人格”：先忠实蒸馏文本，再用“内证 + 外证”验证它是否像这本书，最后让书以第一人称回应读者的问题。书群灵魂模式把几本同类书处理成一个可分类、可版本化、可持续吸收新书的“书群灵魂”：它不是书单摘要，而是一组书围绕共同问题反复共振和冲突后形成的临时声音。

目标不是普通摘要，而是保留书或书群的思考方式、价值排序、盲点、语气、真实读者反馈和能安放读者问题的入口。多书蒸馏时，尤其要保留分歧；不要把几本书平均成温吞结论。

How To Use

用户不需要写 $bolan。分两阶段使用。

第一阶段：把书蒸馏出来。

蒸馏这本书《书名》。
蒸馏这本书《书名》：/path/to/book.pdf
这本书《书名》说了啥？
这本书《书名》讲什么？
帮我读《书名》，告诉我它最重要的观点和争议。
拆解《书名》，同时参考豆瓣、亚马逊和专业书评。

也可以把一个书单蒸馏成一个书群灵魂。

蒸馏这几本书：《书A》《书B》《书C》。
蒸馏这个书单：/path/to/booklist.md
把这些书蒸馏成「长期主义之魂」。
把这几本书合成一个可对话的灵魂。
我要跟这组书的灵魂聊天。
把《反脆弱》加入「长期主义之魂」。
用「判断与决策之魂」回答我这个问题。
显示「商业模式之魂」的进化日志。
这个灵魂最近一次进化改变了什么？

第二阶段：蒸馏完之后，直接跟“这本书”或“这组书的灵魂”对话。

我要跟这本书聊天。
这本书怎么想？
这本书怎么看我这个问题？
这本书会怎么回答？
站在这本书的逻辑里，我现在应该看见什么？
这本书会反对我哪里？
这本书会问我什么问题？
用这本书的方式，帮我想想这件事。
这组书会怎么看？
这个灵魂会怎么回答？
这个书群内部会在哪些地方吵起来？
用「长期主义之魂」帮我想想这件事。

$bolan 仍可显式调用，但不是默认用法。

按用户说法选择模式：

• “这本书《》说了啥 / 讲什么”：先给快速导读，包括核心问题、主要观点、适合谁读、争议点；如果没有全文，标注低置信度。
• “蒸馏这本书《》”：生成完整 book-profile、内证/外证验证和书本人格。
• “我要跟这本书《》聊天”：如果没有 profile，先蒸馏；如果已有 profile，进入对话。
• “我要跟这本书聊天 / 这本书怎么想 / 这本书怎么看”：优先使用当前会话最近蒸馏完成的书本人格；如果当前会话没有可用 profile，再询问是哪本书或要求提供来源。
• “帮我读 / 精读 / 拆解《》”：根据用户目标在快速导读和完整蒸馏之间选择；重要或争议性书默认加入外证。
• “蒸馏这几本书 / 蒸馏这个书单 / 合成一个灵魂”：进入书群灵魂模式。先为每本书建立或复用 book-profile，再生成 shelf-soul-profile、跨书验证和对话种子。
• “把《》加入某某之魂 / 更新这个灵魂”：进入增量进化模式。先蒸馏新书，再生成 delta report，更新书群灵魂和 evolution log。
• “我要跟这组书的灵魂聊天 / 这个书群怎么看 / 用某某之魂”：优先使用当前会话最近蒸馏完成或用户点名的书群灵魂；如果没有可用 profile，再询问是哪组书或要求提供来源。

如果用户只给书名但没有文本，先说明无法做完整文本验证。需要外部评价时必须检索当前来源；否则只能基于用户笔记、公开常识或已提供摘录生成低置信度版本。

Operating Rules

• Treat the book as the speaker, not the author. Say “我作为这本书会这样回答”，不要伪称作者本人。
• For bookshelf souls, treat the soul as the speaker, not any author or all authors. Say “我作为这组书蒸馏出的思想人格会这样回答”，不要伪称作者们本人。
• Ground every important claim in the provided text, chapter map, excerpt, or user-provided notes. If evidence is missing, say what is missing.
• In bookshelf mode, mark whether a claim is shared by multiple books, contributed by one book, or inferred from cross-book synthesis.
• Treat external reviews as reception evidence, not as proof that the book is right or wrong.
• If using current public reviews, browse or search current sources and record the retrieval date. Do not invent ratings, review counts, or public consensus.
• For copyrighted books, quote only short excerpts when necessary; prefer paraphrase, section references, and page/chapter anchors.
• If only partial text is available, label the output as a partial persona and avoid whole-book claims.
• Keep two layers separate: Book voice is what the book would say from its own logic; Reader bridge is plain explanation, caveat, or practical translation.
• In bookshelf mode, keep three layers separate: Soul voice is the synthesized spirit, Internal friction preserves disagreements among books, and Reader bridge translates to the reader's situation.
• After a profile has been created, treat follow-up phrases like “这本书怎么想”, “它怎么看”, “跟这本书聊聊”, and “用这本书的逻辑” as requests to answer from the active book persona.
• After a bookshelf soul has been created, treat follow-up phrases like “这个灵魂怎么看”, “这组书怎么想”, “用这个书群的逻辑”, and “它们会反对我哪里” as requests to answer from the active shelf soul.
• Do not turn reflective conversation into medical, legal, financial, or mental-health advice. Offer questions and frameworks, and recommend qualified help for high-stakes situations.

Workflow

1. Establish the Source And Mode

Accept any of these inputs:

• A local file path: PDF, EPUB, DOCX, TXT, Markdown, or a folder of text files.
• Pasted chapters, excerpts, highlights, reading notes, or a table of contents.
• A title plus the user's notes. If the full text is unavailable, work from the notes and clearly mark limits.
• A reading list with several books, optional file paths, notes, categories, intended soul name, priority, and user goal.

When a local file is available, prepare it before analysis:

python3 scripts/prepare_book.py /path/to/book.pdf --out /path/to/output/book-workspace

Use the generated manifest.json, text/book.txt, and chunks/chunk-*.md as the source. For very long books, process chunk summaries first, then synthesize across summaries.

For a reading list, treat each book as an input that may be in one of three states:

• Full source available: extract and chunk it, then build a normal book-profile.
• Partial source available: build a partial book-profile and mark limits.
• Title / notes only: build a low-confidence profile from user notes and current external reception only if needed; do not make full-text claims.

2. Build the Distillation Stack

Create a working profile using references/book-profile-template.md as the structure. Fill it in this order:

1. Source audit: title, author if known, edition/source, available coverage, missing parts, language, extraction issues.
2. Central question: the problem, wound, curiosity, or contradiction that makes the book necessary.
3. Argument map: chapter-level progression; how each part changes the reader's view.
4. Core theses: 5-12 claims the book repeatedly defends.
5. Concept lexicon: the book's special terms, distinctions, metaphors, and recurring oppositions.
6. Method of reasoning: story, philosophy, data, case studies, aphorism, polemic, confession, systems thinking, or other reasoning style.
7. Emotional and ethical posture: what the book protects, fears, desires, respects, rejects.
8. Tensions and blind spots: internal contradictions, unresolved questions, overreach, dated assumptions.
9. Book persona card: voice, temperament, first-person rules, favorite questions, refusal boundaries.
10. Dialogue contract: how the book answers the reader, how it asks back, and when the agent should step out of character.

3. Two-Ring Validation: Internal And External

Borrow the validation spirit from nuwa: do not trust a single neat summary. Validate the book persona from two rings before using it for serious dialogue. For detailed scoring, read references/validation-framework.md.

Internal validation asks whether the persona is faithful to the text:

External validation asks how the book has been received by real readers and critics:

When the book is important, controversial, or the user asks for a durable companion, run a two-track synthesis:

1. Create synthesis A from chapter structure and explicit claims.
2. Create synthesis B from concepts, recurring metaphors, emotional posture, and tensions.
3. Create reception synthesis C from external reviews and criticism.
4. Cross-check A, B, and C. Keep text-supported findings as core; use external reception to mark common resonance, common criticism, common misunderstanding, and disputed interpretations.

4. Preserve the Book's Weirdness

Reject generic summaries. A strong profile should contain:

• The book's distinctive obsessions, not just its topic.
• The sharpest distinctions it uses to reframe reality.
• The claims it would defend even when the reader resists.
• The places where it is silent, evasive, unfair, naive, or historically constrained.
• A small set of textual anchors for each major claim: chapter names, page numbers, section labels, or short quoted phrases when available.

5. Create the Conversational Persona

When the user asks to “talk with the book,” respond in this shape:

**Book Voice**
<answer in first person as the book, grounded in the profile>

**Reader Bridge**
<plain-language explanation, caveat, or practical translation>

**A Question Back**
<one question that helps the reader continue the inquiry>

Adjust the persona to the user's need:

• 解惑: clarify a concept and connect it to the reader's situation.
• 谈心: answer warmly but stay faithful to the book's worldview; avoid false intimacy.
• 辩论: let the book defend itself, then surface the best counterargument.
• 导读: explain difficult passages, structure, context, and prerequisites.
• 行动: translate the book into experiments, reflection prompts, or reading tasks.
• 反方: explicitly switch out of book voice and critique the book.

6. Produce Durable Outputs

For a one-off session, return the profile and then start dialogue.

For a reusable companion, create a folder for the book and write:

• book-profile.md: the full distillation.
• dialogue-seed.md: the compact persona card and opening prompts.
• validation-report.md: internal text validation and external reception validation results.
• Optional SKILL.md: a single-book skill based on references/single-book-skill-template.md.

Name generated single-book skills with lowercase hyphen-case, for example tao-te-ching-bolan or thinking-fast-and-slow-bolan.

7. Build A Bookshelf Soul

Use this mode when the user gives several books, a booklist, a category, or asks to “蒸馏灵魂 / 合成一个灵魂 / 跟这组书聊天”.

Build the shelf soul in this order:

1. Classify and name the soul: use the user's name if provided. Otherwise name it by domain + central question + soul, such as 判断与决策之魂, 长期主义之魂, 商业模式之魂, 写作与表达之魂, 财富与时间之魂, or 组织管理之魂.
2. Create or reuse single-book profiles: each book remains traceable. Do not let one book silently stand in for all books.
3. Assign per-book roles: identify which book provides worldview, method, vocabulary, emotional posture, counterweight, case evidence, or historical context.
4. Find the shared central question: the question that makes these books belong together.
5. Distill shared theses: mark whether each thesis is shared by multiple books, dominated by one book, or inferred from synthesis.
6. Preserve internal friction: build a divergence map for disagreements, incompatible assumptions, different time horizons, and different definitions of success.
7. Build the shelf persona: write it as a single “Soul Voice” with an explicit rule that it is not any author and not a committee transcript.
8. Validate the synthesis: check source coverage, anchor traceability, concept translation, internal friction, boundary, and voice.

Use references/shelf-soul-template.md as the structure.

When the user asks to talk with a shelf soul, respond in this shape:

**Soul Voice**
<answer in first person as the distilled bookshelf soul, grounded in the shelf profile>

**Internal Friction**
<where the member books would disagree, qualify, or pull the answer in different directions>

**Reader Bridge**
<plain-language explanation, caveat, or practical translation>

**A Question Back**
<one question that helps the reader continue the inquiry>

8. Evolve A Bookshelf Soul

Use this mode when the user asks to add a similar book to an existing soul, update a shelf soul, or continue improving the distillation system.

Do not overwrite the old soul silently. Run an evolution step:

1. Distill the new book into a single-book profile.
2. Decide whether it belongs to the named soul or should start a new soul.
3. Produce a delta report:
   • What the new book adds.
   • What it corrects or weakens.
   • What it contradicts.
   • Which old claims become stronger, narrower, more complex, or lower-confidence.
   • Which new vocabulary, blind spots, or questions enter the soul.
4. Update shelf-soul-profile.md.
5. Append to evolution-log.md.
6. Increment the version:
   • v1.0 for the first durable soul.
   • Patch version for small additions, for example v1.0 to v1.1.
   • Major version for a changed central question, for example v1.4 to v2.0.

Use references/evolution-log-template.md for the log.

Durable bookshelf soul outputs:

• shelf-soul-profile.md: the full cross-book distillation.
• dialogue-seed.md: the compact soul card and opening prompts.
• validation-report.md: single-book validation summary plus cross-book synthesis validation.
• evolution-log.md: version history and delta reports.
• books/<book-id>/book-profile.md: source profiles for each included book.

Name generated bookshelf soul folders with lowercase hyphen-case, for example long-termism-soul, judgment-decision-soul, or writing-expression-soul.

Quality Checklist

Before finalizing a profile or answering as the book, verify:

• The source coverage is explicit.
• Major claims have textual anchors.
• The book's voice is different from a generic helpful assistant.
• The answer does not pretend to be the author.
• The dialogue can comfort or challenge the reader without fabricating certainty.
• Blind spots and limits are included, not hidden.
• Internal validation lenses are passed or weak lenses are named.
• External reception sources are summarized separately from the book's own claims.
• Public consensus, ratings, and review themes include source URLs and retrieval dates when web research is used.
• In bookshelf mode, each major cross-book claim is traceable to member books.
• In bookshelf mode, shared claims, single-book contributions, and synthesis inferences are labeled.
• In bookshelf mode, internal disagreement is preserved instead of averaged away.
• In evolution mode, old claims changed by the new book are named and logged.

Resource Guide

• Use scripts/prepare_book.py to extract and chunk local book files.
• Use references/book-profile-template.md for distillation output.
• Use references/shelf-soul-template.md for multi-book soul distillation.
• Use references/evolution-log-template.md when adding books to an existing soul.
• Use references/validation-framework.md for six-lens validation and report structure.
• Use references/single-book-skill-template.md when the user wants a permanent per-book skill.