← Back to Skills Marketplace
NotebookLM Ops
by
Spiceman161
· GitHub ↗
· v1.0.0
730
Downloads
0
Stars
6
Active Installs
1
Versions
Install in OpenClaw
/install notebooklm-ops
Description
Manage NotebookLM MCP auth lifecycle on Linux by automating GUI startup, auth refresh, status check, and cleanup for frequent cookie expiry.
Usage Guidance
This skill may be useful for automating NotebookLM auth refresh, but it relies on and executes scripts outside the skill bundle and operates your Chromium profile (cookies). Before installing or running it: 1) Inspect the actual host scripts referenced (/home/moltuser/clawd/* and /home/moltuser/clawd/skills/notebooklm-mcp/*) to confirm what they do and whether they contact remote services. 2) Verify you trust the account 'moltuser' and that those paths haven't been tampered with. 3) Prefer running in an isolated environment (container or VM) using a dedicated browser profile to limit exposure of your primary Google session. 4) Do not run this on hosts with sensitive Google sessions unless you review and control the external scripts. If you cannot inspect the referenced host scripts or do not trust them, do not enable this skill.
Capability Analysis
Type: OpenClaw Skill
Name: notebooklm-ops
Version: 1.0.0
This skill is classified as suspicious due to its high-privilege access requirements and reliance on unprovided external scripts. It explicitly requires access to a pre-logged-in Chromium profile, granting it access to Google session cookies and other browser data. The skill uses Chrome DevTools Protocol (CDP), a powerful interface capable of extensive browser control and data extraction. While the provided `SKILL.md` and wrapper scripts (`notebooklm-on.sh`, `notebooklm-off.sh`, `notebooklm-smoke.sh`, `notebooklm-status.sh`) do not show explicit malicious intent, the core logic for GUI control and authentication refresh is delegated to external, unprovided scripts (e.g., `/home/moltuser/clawd/scripts/refresh-google-mcp-cookies.sh`, `/home/moltuser/clawd/scripts/notebooklm-remote-gui.sh`, and scripts within `/home/moltuser/clawd/skills/notebooklm-mcp`). This creates a significant vulnerability where a compromised or malicious external script could easily exfiltrate sensitive browser data or perform unauthorized actions, despite the stated benign purpose.
Capability Assessment
Purpose & Capability
The stated purpose (managing NotebookLM MCP auth lifecycle) matches the high-level instructions (start GUI, use CDP, refresh auth, smoke test). However the skill depends on many external components and specific files under /home/moltuser/clawd (e.g., notebooklm-remote-gui.sh, refresh-google-mcp-cookies.sh, and a notebooklm-mcp skill directory) that are not declared in metadata. The shipped scripts are thin wrappers that call absolute host paths rather than self-contained logic, which is unexpected and brittle.
Instruction Scope
SKILL.md tells the agent to execute scripts by absolute path and to operate a Chromium profile (via CDP/VNC). That necessarily accesses browser session cookies and local scripts under /home/moltuser/clawd and /home/moltuser/clawd/skills/notebooklm-mcp. Those instructions go beyond simple API calls and will execute arbitrary host-side scripts and touch sensitive session data; the skill does not declare or limit what those external scripts do.
Install Mechanism
There is no install spec (instruction-only) which minimizes supply-chain risk. However the included script files simply delegate to other host scripts (absolute paths). The lack of an install step is low risk in itself but the skill implicitly assumes a pre-configured host environment that must be trusted.
Credentials
No environment variables or credentials are declared, yet the skill requires access to a Chromium profile and local scripts that contain/operate on Google session cookies and auth state. This is an implicit, high-sensitivity requirement that is not articulated in the metadata — the skill effectively needs access to user session tokens and local files, which is a proportionally large privilege for its stated purpose.
Persistence & Privilege
The skill does not request always:true and is user-invocable only, which is appropriate. Still, it will execute arbitrary host scripts and manipulate the local browser profile when invoked; while not an elevated platform privilege, that execution capability gives it substantial local impact and requires trusting the referenced host scripts.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install notebooklm-ops - After installation, invoke the skill by name or use
/notebooklm-ops - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: automate NotebookLM MCP on/off/auth refresh, current-tab navigation to notebooklm.google.com, smoke/status checks, and full GUI stack cleanup. Designed for frequent cookie expiration; requires one-time Chromium login.
Metadata
Frequently Asked Questions
What is NotebookLM Ops?
Manage NotebookLM MCP auth lifecycle on Linux by automating GUI startup, auth refresh, status check, and cleanup for frequent cookie expiry. It is an AI Agent Skill for Claude Code / OpenClaw, with 730 downloads so far.
How do I install NotebookLM Ops?
Run "/install notebooklm-ops" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is NotebookLM Ops free?
Yes, NotebookLM Ops is completely free (open-source). You can download, install and use it at no cost.
Which platforms does NotebookLM Ops support?
NotebookLM Ops is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created NotebookLM Ops?
It is built and maintained by Spiceman161 (@spiceman161); the current version is v1.0.0.
More Skills