← Back to library

Research a topic from 20 videos with cited Obsidian notes

Artem Zhutov liked NotebookLM's cited answers but hated adding sources one by one and losing citations on copy-out. His Claude Code skill searches YouTube from the terminal, loads about twenty chosen videos, asks questions and writes cited answers into linked Obsidian notes.

  • OutcomeAsk questions across a hand-picked set of videos and keep every answer, with its citations, as linked notes in your vault.
  • SetupAn afternoon+
  • LevelAdvanced
  • CreditArtem Zhutov
View original
Works with
Claude CodeGemini

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

When should you use it?

  • You research by watching many videos
  • You lose track of which source said what
  • Your notes already live in an Obsidian vault

Not for: Topics where video sources are unreliable; People who prefer a browser-only workflow

What do you need, and what do you get?

You need

  • Topic and search terms
  • Command-line tools for YouTube search and NotebookLM
  • An Obsidian vault

You get

  • Notebook loaded with chosen sources
  • Cited answers saved as notes
  • Topic and source notes linked to each other

How does it work, step by step?

  1. Search and chooseSearch YouTube from the terminal and pick the videos yourself to keep noise low.
  2. Load the notebookAdd the chosen videos as sources in one command.
  3. Ask your questionsQuery the notebook, including what the sources leave out.
  4. Write to the vaultSave each source and topic as its own note, with citations becoming links.
  5. Walk the graphOpen a topic note to see which videos mention it and follow the links.

The prompt

Our own prompt, inspired by Artem Zhutov and written to work in Claude Code and Gemini. Values in lime are placeholders.

Prompt0 variables
Search YouTube for videos about [topic] and show me the top 30 with channel and date. I will pick about 20. Create a NotebookLM notebook with those as sources. Ask it: what are the main approaches, where do the sources disagree, and what do none of them cover? Save each answer to my Obsidian vault with citations, one note per source video and one per topic, linking topics to the sources that mention them.

Inspired by Artem Zhutov: Claude Code + NotebookLM + Obsidian: The Research Stack Nobody's Using. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Letting the tool suggest sources reintroduces noise; picking them yourself was the point.
  • Answers only cover what the chosen videos say, so gaps in selection become gaps in findings.

Our take

Treating the research notebook as a back end rather than a destination is the move worth copying. Answers leave the browser tab and land in a vault you already open. Choosing sources by hand matters more than it looks. Artem's skill fixes two specific annoyances: adding sources one by one and losing citations when answers are copied out. Searching YouTube from the terminal and picking about twenty videos yourself keeps the notebook focused; letting a tool suggest sources reintroduces the noise he wanted to avoid. Ask questions that include what the sources leave out, since answers only cover what the chosen videos say. Writing each source and topic as its own note, with citations turned into links, means the graph shows which videos support which ideas. Follow those links back to the original timestamps before quoting anything. Video is a weak source for some topics, so check claims elsewhere when accuracy matters. If you prefer to stay in the browser, NotebookLM on its own is simpler.

Where the time goes back: Twenty tabs of copy and paste become a few commands, and the citations survive into your notes.

FAQ

Why not ask Claude directly?
The notebook answers only from your sources, with citations, across far more of them.
How many sources?
The author used twenty videos; the notebook tool allows many more.

Source and credit

Inspired by Artem Zhutov. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Claude Code + NotebookLM + Obsidian: The Research Stack Nobody's Using
Creator
Artem Zhutov
Published on
artemxtech.substack.com (Substack)
Original date
Feb 24, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude Code
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminRoutine✓ AI dry run

Draft a weekly recap post from your GitHub activity

Start Monday with a ready draft of what you shipped last week, plus a stats page, instead of trying to remember.

Credit: Yash Kumar Saini

An afternoon+
Operations & AdminPrompt✓ AI dry run

Rewrite a task prompt to go deeper, not bigger

Before handing an AI an important piece of work, have it explain how a leading practitioner would approach the job, which raw inputs and methods they would use, and what independent check would prove the answer right, then rewrite your request around those answers before any work starts.

Credit: Felix Rieseberg

Minutes
Operations & AdminSkill✓ AI dry run

Stress-test an idea with an honest devil's advocate

Get an AI to argue against your plan one serious objection at a time, offer real alternatives with tradeoffs, and openly mark each concern as resolved, narrowed or still open, so you end with a stronger plan or a better one.

Credit: u/wtfzambo on r/ChatGPTPromptGenius

Minutes
Operations & AdminWorkflow✓ AI dry run

Build a paper's data pipeline with a coding agent

Hand the collection, cleaning and charting code for a research project to an agent while you review it in your editor and notebooks.

Credit: Kevin Yang

Under an hour
Operations & AdminWorkflow✓ AI dry run

Get agent-written browser tests that survive CI

Get a Playwright test written by Claude Code against your running app, reviewed twice, repeated to catch flakiness and committed beside its plain-English scenario.

Credit: Jakob Norlin

Under an hour