notebooklm-manager

Manage NotebookLM notebook registries via Chrome agent delegation.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/i0switch/yoyaku-tosho --skill notebooklm-manager-i0switch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notebooklm-manager
Source: https://github.com/i0switch/yoyaku-tosho/tree/main/.github/skills/notebooklm-manager
Command: npx skills add https://github.com/i0switch/yoyaku-tosho --skill notebooklm-manager-i0switch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

NotebookLM management can involve scattered manual steps including querying notebooks, maintaining a registry, and coordinating browser interactions. This skill centralizes and automates those tasks via a Chrome agent, reducing manual overhead and keeping notebook data synchronized.

Core Features & Use Cases

  • Notebook orchestration: query, add, list, search, enable/disable, and remove notebooks through a centralized workflow.
  • Registry management: maintain a notebook registry with id, URL, and status for quick discovery and operations.
  • Safe Chrome interactions: delegates all NotebookLM URL handling to the agent, avoiding direct navigation by manual tooling.

Quick Start

Provide a NotebookLM URL or a command to add, query, or list notebooks and let the agent manage the workflow.

Frequently Asked Questions about notebooklm-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate NotebookLM notebook management through a Chrome agent?

NotebookLM notebook management automation uses a Chrome agent to orchestrate workflows, enabling you to add, query, list, and remove notebooks via centralized commands instead of manual browser interactions. It maintains a synchronized registry for quick discovery.

Do I need claude --chrome and claude-in-chrome MCP to manage NotebookLM notebooks?

Yes, managing NotebookLM notebooks requires claude --chrome with claude-in-chrome MCP to delegate browser interactions safely. This setup ensures auditable Chrome sessions and prevents direct URL navigation by manual tooling.

How does registry management work for NotebookLM notebooks?

Registry management for NotebookLM notebooks maintains a centralized record of notebook IDs, URLs, and statuses. This registry enables quick discovery and allows the Chrome agent to execute operations like enabling, disabling, or removing notebooks across project scopes.

Can I add a NotebookLM notebook to the registry using a URL?

Yes, you can add NotebookLM notebooks to the registry by providing a URL. The Chrome agent processes the URL input, registers the notebook with its ID and status, and makes it available for querying and listing operations.

What are the limitations of using a Chrome agent for NotebookLM orchestration?

The primary limitation of Chrome agent NotebookLM orchestration is the strict boundary against direct NotebookLM URL navigation by manual tooling. All interactions must route through the agent using a specified data-path for safe, auditable storage.