Deep Dive

How It Works

1. Video, URL, or topic: YouTube transcript, article, talk, or a topic to research
2. Extract content: Pull transcript / fetch page / search authoritative source
3. Extract key insights: Core thesis · ranked insights · frameworks · surprising claims
4. Map to your projects: Which projects apply · what changes · what to file away
5. Integration plan: Immediate (≤5) · near-term · long-term · explicit discards
6. Store to Akashic + sync: mind_remember + scp md/html to the Mini for the Intel Hub
7. Markdown + HTML report: Indexable .md + Mission Control-themed companion to deep-dives/

Invocation Triggers

Use Cases

• Have Claude watch a two-hour talk and hand you the five insights that matter
• Give Claude eyes: browser screenshots and sampled frames when the visuals carry the message
• Turn any video, article, or topic into an integration plan mapped to your actual projects

The Problem

You watch a two-hour talk, nod at three good ideas, and forget all three by the next morning. The insight that would have changed how you build never makes it to a project, because there is no bridge between consuming content and acting on it. A month later you re-watch the same video because nothing was captured, nothing was mapped, and nothing was filed away as not-for-you. The cost is not the watching. It is watching the same thing twice.

What It Does

1. 1
   Pull the words

   Claude extracts the full transcript — the subtitle track for a video, the page content for an article, the most authoritative source for a topic. Full input, not a skim — the core thesis is usually buried mid-source.

2. 2
   Give it eyes

   Words are not always the message. Claude drives a real browser with Playwright, screenshots the key moments, and reads the frames as images. For raw video files it samples frames with ffmpeg. Charts, demos, and slides get seen, not guessed at.

3. 3
   Extract ranked insights

   The core thesis, the top five to seven insights ranked by novelty and applicability, the reusable frameworks, the evidence and data points, and the claims that challenge conventional wisdom.

4. 4
   Map each insight to your projects

   For every insight: which of your projects does it touch, what would change if you applied it, what would you start and stop. Insights that fit nothing get filed explicitly under not-applicable — that section is never empty.

5. 5
   Write the integration plan

   Immediate, near-term, long-term, and discard. Immediate is capped at five ruthless tasks — what specifically changes this week — not a backlog dump.

6. 6
   File it in your knowledge base

   The report is written to disk and stored where your future sessions can recall it, so the next "have I seen this before?" is a lookup, not a re-watch.

What You Get / What It Doesn't Do

Tips

Get the Skill