notebooklm-manager

# NotebookLM Manager Query orchestration and notebook registry management. ## Instructions ### Tool Boundaries Chrome MCP tools (`mcp__claude-in-chrome__*`) aren't in this skill's allowed tool set — calling them directly will error. All browser interaction goes through the chrome-mcp-query agent via Task. If the agent returns an error, don't attempt Chrome tools yourself. ### 0. Data Path Resolution (run first) Read `~/.claude-code-zero/notebooklm-connector/data-path` to obtain `DATA_DIR`. The PreToolUse hook automatically detects install scope (project vs user) and writes the correct path. - The file contains a single line: the absolute path to the data directory. - Store this as `{DATA_DIR}` and use it for ALL subsequent file operations. - **File read error → Tell user to restart the session (hook may not be loaded).** ### 0.1 Config Read `{DATA_DIR}/config.json` for user preferences: - `max_followups`: Maximum follow-up queries in coverage analysis (default: 3) - `max_query_length`: Maximum characters per query sent to NotebookLM (default: 40000) - `language`: Preferred response language (null = match user's language) - `auto_coverage`: Enable automatic coverage analysis (default: true) If the file is missing or a field is absent, use defaults above. ### 1. Query Detection Extract from user message: - `notebook_id`: Which notebook (e.g., "claude-docs") - `question`: What to ask ### 2. Notebook Lookup Read `{DATA_DIR}/library.json` to find notebook URL. - **Fil...