Deep Dive
Ad-hoc research from YouTube videos, URLs, or topics. Extracts knowledge, maps it to your ecosystem, and produces an integration plan.
How It Works
- Video, URL, or topic: YouTube transcript, article, talk, or a topic to research
- Extract content: Pull transcript / fetch page / search authoritative source
- Extract key insights: Core thesis · ranked insights · frameworks · surprising claims
- Map to your projects: Which projects apply · what changes · what to file away
- Integration plan: Immediate (≤5) · near-term · long-term · explicit discards
- Store to Akashic + sync: mind_remember + scp md/html to the Mini for the Intel Hub
- Markdown + HTML report: Indexable .md + Mission Control-themed companion to deep-dives/
Invocation Triggers
/deep-divewatch thisresearch this videolearn from thisstudy thisUse Cases
- Extract knowledge from a YouTube talk and map it to your projects
- Research a topic and produce an actionable integration plan
- Turn a conference talk or article into concrete next steps
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
- 1Extract the source content
Pull the full YouTube transcript, fetch the article via WebFetch, or search for the most authoritative source on a topic. Full input, not a skim — the core thesis is usually buried mid-source.
- 2Extract ranked insights
Pull 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.
- 3Map each insight to your projects
For every insight: which project 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.
- 4Write 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.
- 5Emit markdown plus HTML companion
Write the .md with frontmatter for Akashic indexing, then render the Mission Control-themed HTML companion off the canonical reports-theme CSS. Both artifacts, same slug, same directory.
- 6Store to Akashic and sync to the Mini
Store the full output via mind_remember with deep-dive plus source-domain plus topic tags, then scp both files to the Mac Mini so the Intel Hub Deep Dives tab can see them. Files on the MacBook are invisible to MC.
What You Get / What It Doesn't Do
- A markdown report with source, thesis, ranked insights, project mapping, and integration plan
- A Mission Control-themed HTML companion at the same slug, CSS inlined and self-contained
- An explicit not-applicable section — insights filed away so they are never re-evaluated
- An integration plan capped at five immediate tasks, each executable without re-reading the source
- An Akashic memory ID referenced in both files, with both synced to the Mac Mini
- Decide what you build — it maps and plans; the call to ship is yours
- Summarize a skim — it processes the full transcript or it does not run
- Publish public content — it stays internal until you route it through deep-dive-to-social
- Survive without the sync — files on the MacBook never reach the Intel Hub
Tips
Understand what is actually relevant to your projects before deciding what to build. Forced relevance produces a plan you will not execute.
Filing an insight as not-for-me is a real output. It stops the next session from re-evaluating the same content from scratch.
If you write it under Immediate, you do it this week or you explicitly move it to near-term. An integration plan you ignore is decoration.
Get the Skill
Unlock the full Deep Dive SKILL.md — drop it into ~/.claude/skills/ and trigger it by name.
- A markdown report with source, thesis, ranked insights, project mapping, and integration plan
- A Mission Control-themed HTML companion at the same slug, CSS inlined and self-contained
- An explicit not-applicable section — insights filed away so they are never re-evaluated
- An integration plan capped at five immediate tasks, each executable without re-reading the source
29 more production skills ready to install.