Back to Details

strategic-reading

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

strategic-reading — Applied Analysis from Source Texts

strategic-reading — 基于原始资料的应用分析

Convention: see conventions/quality.md for citation rules (every recommendation cites the source) and back-link enforcement.
Convention: see _brain-filing-rules.md — output files by primary subject (concepts/ for general strategy, projects/ for problem-tied playbooks).
约定： 请查看 conventions/quality.md 了解引用规则（每条建议都需引用资料来源）和反向链接要求。
约定： 请查看 _brain-filing-rules.md — 按主题分类输出文件（
concepts/
存放通用战略内容，
projects/
存放问题相关手册）。

What this is

功能说明

Take a large text PLUS a specific strategic problem, produce analysis that maps the text's insights onto the problem. This is not book summarization. This is reading with a mission.
Where 
book-mirror
personalizes a book to the reader's whole life, 
strategic-reading
personalizes it to ONE current problem. Same shape (extract → analyze → mirror), different lens.
Canonical example: a power-dynamics history book read against a specific gatekeeper-vs-incumbent fight, producing a tactical analysis that maps the book's playbook onto the situation with counter-tactics and a short/medium/long-term playbook.
输入一份长篇文本以及一个特定战略问题，生成将文本见解与问题匹配的分析内容。这不是书籍摘要工具，而是带着明确目标的针对性阅读。
book-mirror
是将书籍内容与读者的整体生活场景匹配，而 
strategic-reading
则聚焦于单个当前问题。两者流程相似（提取 → 分析 → 匹配），但聚焦视角不同。
典型示例： 以一本权力动态相关的历史书籍为参考，分析特定的“守门人 vs 在位者”对抗场景，生成战术分析报告，将书中的策略框架与当前情况对应，提供反制战术及短期/中期/长期行动手册。

Inputs

输入项

  1. Source text — book (EPUB/PDF), article, transcript, historical case study, any large document.
  2. Strategic problem — the specific situation to analyze through the lens of the text. The user describes this explicitly or it's obvious from context.
  1. 原始资料文本 — 书籍（EPUB/PDF格式）、文章、文字记录、历史案例研究等任何长篇文档。
  2. 战略问题 — 需要结合文本分析的具体场景。用户需明确描述该问题，或问题可从上下文直接推断。

Output

输出

The brain page is the artifact. PDF is a rendering, never primary.
核心产出为脑图页面（brain page），PDF仅为渲染版本，并非核心文件。

Brain page structure

脑图页面结构

markdown
undefined
markdown
undefined

[Source Title] — Applied to [Problem]

[资料标题] — 应用于[问题场景]

One-paragraph executive summary: how the source maps to the situation, the key insight, the bottom line.
一段执行摘要：说明资料内容如何与当前场景匹配、核心见解及最终结论。

The Core Parallel

核心关联

How the source's central dynamic maps onto the user's situation.
资料中的核心动态如何与用户的场景对应。

Chapter / Section Triage

章节/内容筛选

For each major section of the source:
  • 2-3 sentence summary of what it says
  • Relevance to the problem: HIGH / MEDIUM / LOW
  • One directly applicable quote (if any)
针对资料的每个主要章节：
  • 2-3句话总结章节内容
  • 与问题的相关性：高/中/低
  • 一条直接适用的引用（如有）

The Source's Playbook

资料中的策略框架

The author's framework, tactics, or strategies — organized as:
  • What the protagonist DID (tactics)
  • What WORKED and why
  • What FAILED and why
  • What OPPONENTS did that was effective
整理作者提出的框架、战术或策略：
  • 主角采取的行动（战术）
  • 有效的行动及原因
  • 失败的行动及原因
  • 对手采取的有效行动

Counter-Tactics

反制战术

Specific moves from the source that map to the user's situation:
  • What to DO (with source evidence)
  • What to AVOID (with source evidence)
  • What to WATCH FOR (warning signs from the source)
从资料中提取的适用于用户场景的具体举措：
  • 应采取的行动（附资料依据）
  • 应避免的行动（附资料依据）
  • 需要警惕的信号（来自资料中的预警）

Applied Playbook

应用行动手册

The synthesis — actionable recommendations:
  • Short-term (this week / this month)
  • Medium-term (this quarter)
  • Long-term (this year+)
综合分析后的可落地建议：
  • 短期（本周/本月）
  • 中期（本季度）
  • 长期（一年及以上）

Key Quotes

关键引用

Direct quotes from the source that are devastatingly relevant. Maximum 5-10. Quality over quantity.
从资料中选取的高度相关的直接引用，最多5-10条，重质不重量。

See Also

相关链接

Links to relevant brain pages (related concepts, related projects).
undefined
指向相关脑图页面的链接（相关概念、相关项目）。
undefined

Process

流程

Phase 1: Ingest the source
  ├── EPUB: extract chapters via BeautifulSoup (see book-mirror SKILL.md
  │   for the extraction pipeline)
  ├── PDF: pdftotext -layout
  ├── Article: web_fetch
  └── Identify Table of Contents and total size.

Phase 2: Triage chapters
  ├── Read first 2000 chars of each chapter.
  ├── Classify relevance to the problem (HIGH / MEDIUM / LOW).
  └── HIGH chapters get full reads. MEDIUM partial. LOW skipped.

Phase 3: Deep read HIGH chapters
  ├── Tactics and strategies used.
  ├── Power dynamics and how they shifted.
  ├── Specific quotes that map to the problem.
  └── Moments where the protagonist's approach succeeded or failed.

Phase 4: Synthesize
  ├── Map source insights onto the specific problem.
  ├── Build the playbook (do / avoid / watch for).
  ├── Generate short/medium/long-term recommendations.
  └── Select the most devastating quotes.

Phase 5: Write and deliver
  ├── Write the brain page at the right location:
  │     • If problem-specific: projects/<slug>/playbook.md
  │     • If general strategy: concepts/<slug>.md
  ├── put_page via the standard CLI flow.
  └── Optional: render to PDF via skills/brain-pdf.
阶段1：导入资料
  ├── EPUB：通过BeautifulSoup提取章节（提取流程详见book-mirror SKILL.md）
  ├── PDF：使用pdftotext -layout命令提取
  ├── 文章：通过web_fetch获取
  └── 识别目录及总篇幅。

阶段2：章节筛选
  ├── 阅读每个章节的前2000字符。
  ├── 分类章节与问题的相关性（高/中/低）。
  └── 高相关性章节完整阅读，中相关性章节部分阅读，低相关性章节跳过。

阶段3：深度阅读高相关性章节
  ├── 记录使用的战术和策略。
  ├── 分析权力动态及其变化。
  ├── 提取与问题匹配的具体引用。
  └── 记录主角策略成功或失败的关键节点。

阶段4：综合分析
  ├── 将资料见解与特定问题匹配。
  ├── 构建行动手册（应做/避免/警惕）。
  ├── 生成短期/中期/长期建议。
  └── 筛选最具相关性的引用。

阶段5：撰写并交付
  ├── 在指定位置撰写脑图页面：
  │     • 若为问题专属：projects/<slug>/playbook.md
  │     • 若为通用战略：concepts/<slug>.md
  ├── 通过标准CLI流程执行put_page操作。
  └（可选）：通过skills/brain-pdf渲染为PDF格式。

Quality bar

质量标准

  • Every recommendation must cite the source. Don't say "go direct to the mayor" — say "go direct to the mayor, because when the protagonist refused to be intimidated by a resignation threat (Ch 48), the bluff that worked on five mayors finally failed."
  • Direct quotes are mandatory. The source's own words carry more weight than paraphrase.
  • The analysis must be actionable. Not "this is interesting" but "do this, avoid that, watch for this."
  • Short/medium/long-term breakdown is mandatory. The user needs to know what to do tomorrow AND what to do this year.
  • 每条建议必须引用资料来源。不能只说“直接找市长”，而要说“直接找市长，因为当主角拒绝被辞职威胁吓倒时（第48章），曾对五位市长奏效的虚张声势最终失败了。”
  • 必须包含直接引用。资料原文的说服力远强于转述。
  • 分析必须具备可落地性。不能只说“这很有趣”，而要明确“应做什么、避免什么、警惕什么”。
  • 必须划分短期/中期/长期建议。用户需要知道明天该做什么，以及今年该做什么。

What this skill is NOT

本技能不适用场景

  • Not a book summary tool. Use a different skill (or 
    book-mirror
    for personalized analysis) for general summaries.
  • Not a research tool. Use 
    perplexity-research
    for finding new information about a topic.
  • Not academic literary analysis. No one cares about literary merit — only strategic application.
  • 不是书籍摘要工具。如需通用摘要，请使用其他技能（或使用
    book-mirror
    获取个性化分析）。
  • 不是研究工具。如需查找某主题的新信息，请使用
    perplexity-research
    。
  • 不是学术文学分析工具。无人关注文学价值，仅聚焦战略应用。

Related skills

相关技能

  • skills/book-mirror/SKILL.md
    — book personalized to whole life (vs problem)
  • skills/perplexity-research/SKILL.md
    — current-intel cross-reference for fresh data
  • skills/conventions/quality.md
    — citation + back-link rules
  • skills/book-mirror/SKILL.md
    — 将书籍与读者整体生活场景匹配（而非单个问题）
  • skills/perplexity-research/SKILL.md
    — 用于获取最新数据的跨参考研究工具
  • skills/conventions/quality.md
    — 引用及反向链接规则

Contract

服务协议

This skill guarantees:
  • Routing matches the canonical triggers in the frontmatter.
  • Output written under the directories listed in 
    writes_to:
    (when applicable).
  • Conventions referenced (
    quality.md
    , 
    brain-first.md
    , 
    _brain-filing-rules.md
    ) are followed.
  • Privacy contract preserved: no real names, no fork-specific filesystem path literals, no upstream-fork references.
The full behavior contract is documented in the body sections above; this section exists for the conformance test.
本技能保证：
  • 路由与前言中的标准触发条件匹配。
  • 输出文件存放在
    writes_to:
    指定的目录下（如适用）。
  • 遵循所引用的约定（
    quality.md
    、
    brain-first.md
    、
    _brain-filing-rules.md
    ）。
  • 遵守隐私协议：不使用真实姓名、不包含fork专属文件系统路径字面量、不引用上游fork。
完整行为协议已在上述正文部分说明；本部分用于一致性测试。

Output Format

输出格式

The skill's output shape is documented inline in the body sections above (see "Output", "Brain page format", or equivalent). The literal section header here exists for the conformance test (
test/skills-conformance.test.ts
).
技能的输出格式已在上述正文部分说明（详见“输出”、“脑图页面格式”或对应章节）。本标题的存在是为了一致性测试（
test/skills-conformance.test.ts
）。

Anti-Patterns

反模式

The full anti-pattern list is in the body sections above; this header exists for the conformance test if the body uses a different casing.
完整的反模式列表已在上述正文部分说明；本标题的存在是为了在正文使用不同大小写时进行一致性测试。