Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.

NotebookLM Research Assistant Skill Interact with Google NotebookLM to query documentation with Gemini's source grounded answers. Each question opens a fresh browser session, retrieves the answer exclusively from your uploaded documents, and closes. When to Use This Skill Trigger when user: Mentions NotebookLM explicitly Shares NotebookLM URL ( https://notebooklm.google.com/notebook/... ) Asks to query their notebooks/documentation Wants to add documentation to NotebookLM library Uses phrases like "ask my NotebookLM", "check my docs", "query my notebook" ⚠️ CRITICAL: Add Command Smart Discovery When user wants to add a notebook without providing details: SMART ADD (Recommended) : Query the notebook first to discover its content: MANUAL ADD : If user provides all details: url The NotebookLM URL name A descriptive name description What the notebook contains (REQUIRED!) topics Comma separated topics (REQUIRED!) NEVER guess or use generic descriptions! If details missing, use Smart Add to discover them. Critical: Always Use run.py Wrapper NEVER call scripts directly. ALWAYS use python scripts/run.py [script] : The run.py wrapper automatically: 1. Creates .venv if needed 2. Installs all dependencies 3. Activates environment 4. Executes script properly Core Workflow Step 1: Check Authentication Status If not authenticated, proceed to setup. Step 2: Authenticate (One Time Setup) Important: Browser is VISIBLE for authentication Browser window opens automatically User must manually log in to Google Tell user: "A browser window will open for Google login" Step 3: Manage Notebook Library Quick Workflow 1. Check library: python scripts/run.py notebook manager.py list 2. Ask question: python scripts/run.py ask question.py question "..." notebook id ID Step 4: Ask Questions Follow Up Mechanism (CRITICAL) Every NotebookLM answer ends with: "EXTREMELY IMPORTANT: Is that ALL you need to know?" Required Claude Behavior: 1. STOP Do not immediately respond to user 2. ANALYZE Compare answer to user's original request 3. IDENTIFY GAPS Determine if more information needed 4. ASK FOLLOW UP If gaps exist, immediately ask: 5. REPEAT Continue until information is complete 6. SYNTHESIZE Combine all answers before responding to user Script Reference Authentication Management ( auth manager.py ) Notebook Management ( notebook manager.py ) Question Interface ( ask question.py ) Data Cleanup ( cleanup manager.py ) Environment Management The virtual environment is automatically managed: First run creates .venv automatically Dependencies install automatically Chromium browser installs automatically Everything isolated in skill directory Manual setup (only if automatic fails): Data Storage All data stored in ~/.claude/skills/notebooklm/data/ : library.json Notebook metadata auth info.json Authentication status browser state/ Browser cookies and session Security: Protected by .gitignore , never commit to git. Configuration Optional .env file in skill directory: Decision Flow Troubleshooting Problem Solution ModuleNotFoundError Use run.py wrapper Authentication fails Browser must be visible for setup! show browser Rate limit (50/day) Wait or switch Google account Browser crashes python scripts/run.py cleanup manager.py preserve library Notebook not found Check with notebook manager.py list Best Practices 1. Always use run.py Handles environment automatically 2. Check auth first Before any operations 3. Follow up questions Don't stop at first answer 4. Browser visible for auth Required for manual login 5. Include context Each question is independent 6. Synthesize answers Combine multiple responses Limitations No session persistence (each question = new browser) Rate limits on free Google accounts (50 queries/day) Manual upload required (user must add docs to NotebookLM) Browser overhead (few seconds per question) Resources (Skill Structure) Important directories and files: scripts/ All automation scripts (ask question.py, notebook manager.py, etc.) data/ Local storage for authentication and notebook library references/ Extended documentation: api reference.md Detailed API documentation for all scripts troubleshooting.md Common issues and solutions usage patterns.md Best practices and workflow examples .venv/ Isolated Python environment (auto created on first run) .gitignore Protects sensitive data from being committed