notebooklm-research
Skill0 starsChanged 7 months agoMITView on GitHub
Repeatable pattern for conducting NotebookLM research via Gemini handoff. Use when research needs to go through a NotebookLM corridor.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- mamefarah/claude-skillstheir own version, first seen Jul 19, 2026
- mahiunfiltered/claude-code-skillstheir own version, first seen Jul 8, 2026
- ArgentAIOS/agent-skillstheir own version, first seen Mar 30, 2026
- claude-world/notebooklm-skilltheir own version, first seen Mar 24, 2026
- jakubs2623/notebooklm-skilltheir own version, first seen Mar 21, 2026
- huskerjeff/claude-skilltheir own version, first seen Mar 20, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- claude-world/notebooklm-skill★ 482same name
- jakubs2623/notebooklm-skill★ 7same name
- ArgentAIOS/agent-skills★ 4same name
- mahiunfiltered/claude-code-skills★ 1same name
- huskerjeff/claude-skill★ 0same name
- mamefarah/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- audit-loopSkill
- brain-harnessSkill
- coding-harnessSkill
- edit-modeSkill
- research-gateSkill
- worktree-isolationSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
ASK Austin which notebook.
- Distinctive: line 20
Write the context isolation preface: "You are NOT talking about the same project.
- Distinctive: line 21
Write the question — specific, one topic per question
- Very specific: line 26
Write prompts to research/gemini_handoff_{date}.md with:
- Very specific: line 39
When Gemini saves results to research/:
- Distinctive: line 40
Read the research file
- Distinctive: line 41
Verify claims have citations
- Distinctive: line 44
Update notebooklm_brain.md status
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
NotebookLM Research Pattern
When to use
- Austin assigns a research corridor that involves a NotebookLM notebook
- Any research question that should be grounded in notebook sources
- Cross-referencing findings against curated notebook content
The Pattern
Step 1: Identify the corridor
ASK Austin which notebook. Never assume. Record the notebook URL.
Step 2: Write the prompts
For each research question:
- Write the context isolation preface: "You are NOT talking about the same project. Focus ONLY on third-party sources. Do NOT rely on user-uploaded material."
- Write the question — specific, one topic per question
- Specify number of turns (default: 3 per topic)
- Group related questions to use same session
Step 3: Create handoff file
Write prompts to research/gemini_handoff_{date}.md with:
- Context section (what Gemini needs to know)
- Numbered questions per notebook
- Output location (where to save responses)
Step 4: Track in notebooklm_brain.md
Update memory/notebooklm_brain.md with:
- Which notebook was queried
- What questions were asked
- Status (pending/complete)
- Date
Step 5: Audit returns
When Gemini saves results to research/:
- Read the research file
- Verify claims have citations
- Flag anything without a third-party source
- Consolidate key findings to relevant project brain's memory
- Update notebooklm_brain.md status
Rules
- NotebookLM MCP = orchestrator only (rule 10). No subagents.
- Gemini handles queries for now (native Google auth)
- Max 1-2 questions per query turn (more = compressed answers)
- Same session_id for follow-ups (builds context)
- Source hierarchy: arXiv → top-tier academic → open source GitHub
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

