Search & ResearchDocumentedScanned

notebooklm-skill

Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-back.

Share:

Installation

npx clawhub@latest install notebooklm-skill

View the full skill documentation and source below.

Documentation

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 () - 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: __CODE_BLOCK_0__ **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]:** __CODE_BLOCK_1__ 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 __CODE_BLOCK_2__ If not authenticated, proceed to setup. ### Step 2: Authenticate (One-Time Setup) __CODE_BLOCK_3__ **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 __CODE_BLOCK_4__ ### 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 __CODE_BLOCK_5__ ## 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: __CODE_BLOCK_6__ 5. **REPEAT** - Continue until information is complete 6. **SYNTHESIZE** - Combine all answers before responding to user ## Script Reference ### Authentication Management (auth_manager.py) __CODE_BLOCK_7__ ### Notebook Management (notebook_manager.py) __CODE_BLOCK_8__ ### Question Interface (ask_question.py) __CODE_BLOCK_9__ ### Data Cleanup (cleanup_manager.py) __CODE_BLOCK_10__ ## 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): __CODE_BLOCK_11__ ## 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: __CODE_BLOCK_12__ ## Decision Flow __CODE_BLOCK_13__ ## 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