notebooklm

Topics in the source

• NotebookLM — Browser Automation
• Step 0: Browser Context Setup (Mandatory)
• Phase 0: Grill-Me Intake (Action-Routing)
• Q1 (root) — Action
• Q2 (depends on Q1) — Notebook identity
• Q3 (depends on Q1) — Action-specific parameter
• Q4 (depends on Q1 = action 3) — Studio custom prompt detail
• Notebook Discovery

Requires: A browser automation environment (Claude Code CLI with computer-use, Claude Chrome Extension, or equivalent). Skill will gracefully fail in non-automation contexts with a clear "not supported" message. Critical: This skill is the only browser-automation skill in the v2 collection. It does NOT follow the research-pack Agent Integrity Rules convention. Different constraints apply (UI dynamics, async generation, login walls). Before any other action, verify browser automation is available: 1. Check whether browser-control tools are loaded in the harness (screenshot, click, find-element, navigate) 2. If unavailable → halt with clear message: "This skill requires browser automation. Currently in {context}. Cannot proceed. Use Claude Code CLI with computer-use, Claude Chrome Extension, or equivalent." 3. If available → take initial screenshot, navigate to https://notebooklm.google.com 4. Detect login wall via screenshot. If login screen detected: halt with "Please log in to NotebookLM in the browser, then re-invoke this skill." Never attempt to handle login automatically. Up to 4 forcing questions, one at a time, dependency-ordered. Most invocations stop at Q3. What do you want

This is an excerpt. Refer to the complete source and its current requirements.