agentleFS
0SxD0SxD/agent-skills-plugin-v01/skills/notebooklm-research/SKILL.md

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

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
  1. Distinctive:

    ASK Austin which notebook.

    line 16
  2. Distinctive:

    Write the context isolation preface: "You are NOT talking about the same project.

    line 20
  3. Distinctive:

    Write the question — specific, one topic per question

    line 21
  4. Very specific:

    Write prompts to research/gemini_handoff_{date}.md with:

    line 26
  5. Very specific:

    When Gemini saves results to research/:

    line 39
  6. Distinctive:

    Read the research file

    line 40
  7. Distinctive:

    Verify claims have citations

    line 41
  8. Distinctive:

    Update notebooklm_brain.md status

    line 44

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. 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."
  2. Write the question — specific, one topic per question
  3. Specify number of turns (default: 3 per topic)
  4. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.