Notebooklm Content

Generate slides, audio overviews, and documents from sources using Google NotebookLM via browser automation. Use when the user wants to (1) create presentati...

Security Scan

The skill's purpose (automating NotebookLM via a local browser relay) is coherent, but the instructions reference sensitive local config (gateway token) and grant the agent powerful browser control without declaring those credentials — this mismatch and the potential to read arbitrary browser content are concerning.

Purpose & Capability

The name and description match the runtime instructions: the skill uses OpenClaw browser relay commands to control Chrome and drive NotebookLM. That capability reasonably requires a browser relay and an active NotebookLM session. However, the skill metadata declares no required credentials or config paths while the reference doc explicitly points to a local config (~/.openclaw/openclaw.json) to obtain a gateway token — an inconsistency between declared requirements and the actual instructions.

Instruction Scope

SKILL.md instructs the agent to take snapshots, click elements, type content, and capture notebook URLs. Those operations necessarily expose page content, open-tab URLs, and potentially user data in NotebookLM. The separate reference instructs using cat ~/.openclaw/openclaw.json to view the gateway.auth.token. Although it warns not to paste the token, pointing operators at a sensitive config file is scope-creep and could lead to token disclosure or misuse. There are no instructions that send data to third-party endpoints, but the agent will have access to arbitrary browser content when run.

Install Mechanism

This is an instruction-only skill with no install spec or code files — lowest installation risk. It relies on the user having the OpenClaw Browser Relay extension and local Gateway running; those are user-side prerequisites rather than install steps performed by the skill.

Credentials

Declared requirements list no env vars or config paths, yet references/chrome-relay-setup.md tells the user where the OpenClaw gateway token lives (~/.openclaw/openclaw.json) and shows a command to extract it. That is a mismatch: sensitive local credentials are implicitly required/used but not declared. The skill's operations (controlling the browser) justify needing access to the relay, but the documentation's direction to read the token file increases risk and should have been reflected in the declared requirements and guidance.

Persistence & Privilege

always:false (good), but the skill enables agent-driven browser automation which grants broad access to the user's open tabs and page content. Autonomous model invocation is allowed (platform default); combined with the ability to control and read browser state and the undocumented token reference, this raises the blast radius if the agent acts without strict user confirmation. The skill does not request permanent presence, but its effective privileges at runtime are high.

What to consider before installing

This skill does what it claims (drives NotebookLM via the OpenClaw browser relay), but it also relies on access to your Chrome session and implicitly on the OpenClaw gateway token stored locally. Before installing/using it: (1) Confirm you trust the skill publisher and avoid pasting gateway tokens anywhere; (2) Prefer running it with a disposable browser profile that is logged into NotebookLM only for this task; (3) Require explicit user confirmation for each run (do not allow fully autonomous runs); (4) Do not run commands that cat or expose ~/.openclaw/openclaw.json in untrusted contexts — treat that token as sensitive; (5) If possible, audit openclaw CLI activity/logs while testing, and limit the extension/gateway to localhost-only access to reduce remote risk.

NotebookLM Content Generator

Automated content generation workflow using Google NotebookLM.

Prerequisites

• OpenClaw Browser Relay extension must be installed in Chrome
• Relay must be connected to local OpenClaw Gateway (default port 18792)
• User must be logged into NotebookLM in Chrome

Quick Start

1. Ensure Browser Relay is Active

User action required:

1. Open Chrome with NotebookLM logged in
2. Click OpenClaw Browser Relay extension
3. Enable relay for the target tab

2. Basic Workflow

1. Navigate to NotebookLM
2. Create or open a notebook
3. Add sources (URLs, text, files)
4. Trigger content generation (slides/audio)
5. Wait for completion
6. Return shareable URL

Commands

Check Connection

openclaw browser status --browser-profile chrome-relay --json

List Tabs

openclaw browser tabs --browser-profile chrome-relay --json

Get Snapshot

openclaw browser snapshot --browser-profile chrome-relay --json --limit 120

Navigate

openclaw browser open --url "https://notebooklm.google.com" --browser-profile chrome-relay

Click Element

openclaw browser click <element-ref> --browser-profile chrome-relay --json

Type Text

openclaw browser type <element-ref> "text content" --browser-profile chrome-relay --json

Take Screenshot

openclaw browser screenshot --browser-profile chrome-relay

Workflow: Generate Slides from Topic

1. Open NotebookLM home

   openclaw browser open --url "https://notebooklm.google.com" --browser-profile chrome-relay
   

2. Create new notebook

   • Find and click "ノートブックを新規作成" or "Create notebook"
   • Get snapshot to find element refs

   openclaw browser snapshot --browser-profile chrome-relay --json --limit 80
   

3. Add sources

   • Click "ソースを追加" or similar
   • For URLs: type URL and submit
   • For text: paste text content

4. Generate slides

   • Find "スライド資料" or "Slides" button in Studio panel
   • Click to start generation
   • Wait for "生成中..." to complete

5. Get result URL

   • Once complete, capture the notebook URL
   • Return shareable link to user

Output Types

Type	Japanese	Element Pattern
Slides	スライド資料	button with "tablet" icon
Audio	音声解説	button with "audio_magic_eraser" icon
Video	動画解説	button with "subscriptions" icon
Mindmap	マインドマップ	button with "flowchart" icon
Report	レポート	button with "auto_tab_group" icon
Quiz	クイズ	button with "quiz" icon

Troubleshooting

Element not found

• Run new snapshot: openclaw browser snapshot --browser-profile chrome-relay --json
• Element refs change on page updates

Relay not connected

• Check Gateway status: openclaw gateway status
• User must enable relay in Chrome extension

Generation stuck

• Wait longer (NotebookLM generation can take 1-3 minutes)
• Check for popups or dialogs

Important Notes

• Never hardcode element refs - They change between sessions
• Always get fresh snapshot before clicking
• User must keep Chrome open during generation
• Report progress to user during long operations