Loading...
Loading...
Read a book, article, transcript, or case study through the lens of a specific strategic problem you're facing. Produces an applied playbook that maps the source onto the problem and gives short/medium/long-term recommendations. NOT for general book summaries.
npx skill4agent add garrytan/gbrain strategic-readingConvention: 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).
book-mirrorstrategic-reading# [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)
## 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.
## See Also
Links to relevant brain pages (related concepts, related projects).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.book-mirrorperplexity-researchskills/book-mirror/SKILL.mdskills/perplexity-research/SKILL.mdskills/conventions/quality.mdwrites_to:quality.mdbrain-first.md_brain-filing-rules.mdtest/skills-conformance.test.ts