Skip to main content
plugin

notebooklm — Claude Code plugin: NotebookLM automation

Drives Google NotebookLM from Claude: reads notebooks, adds sources, generates Studio outputs and creates new notebooks.

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add alirezarezvani/claude-skills
/plugin install notebooklm@claude-code-skills
Open on GitHub

What notebooklm does

The plugin runs on browser automation. It opens NotebookLM, asks a notebook's chat a question and returns the answer, pushes a URL, text, file, Google Doc or synthesized content into a notebook, kicks off Studio generation — Audio Overview, Study Guide, Briefing Doc, FAQ, Mind Map, slides, infographic — and starts a new notebook with a title and initial sources. For the exact Studio set, the plugin tells you to read the live panel: that UI moves fast.

Four actions sit behind a grill-me intake that routes on Q1–Q4 answers. The stdlib scripts do the plumbing: action_router.py turns answers into an action plan and UI flow, custom_prompt_template_generator.py builds a starter prompt from output type and audience, async_action_classifier.py decides whether to wait or notify and move on. A browser-automation persona agent and the /cs-notebooklm slash command come with it.

You need a browser automation environment: Claude CLI with computer-use, the Claude Chrome Extension, or Playwright/Puppeteer with screenshot and click tools. Step 0 checks the environment and exits with a clear "not supported" message when it is missing. Claude.ai web won't run it, because there is no browser automation there. The NotebookLM account is user-provided and the plugin never auto-logs in. UI generation can take 5-10 minutes, so slow operations follow a fire-and-notify pattern instead of blocking.

What it helps with

  • ask a notebook's chat a question and get a clean answer
  • push a URL, text or file into a NotebookLM notebook
  • generate an Audio Overview or Briefing Doc from notebook sources
  • build a Mind Map, slide deck or infographic from the sources
  • create a new notebook with a title and initial sources

Example prompts for the agent

  • open NotebookLM and check my market research notebook
  • add this URL to NotebookLM
  • generate a Video Overview from my notebook

How to install notebooklm

Plugin marketplace

/plugin marketplace add alirezarezvani/claude-skills
/plugin install notebooklm@claude-code-skills

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about notebooklm

How do I install notebooklm in Claude?

Add the marketplace with /plugin marketplace add alirezarezvani/claude-skills, then install the plugin: /plugin install notebooklm@claude-code-skills.

What does notebooklm do?

It controls Google NotebookLM through browser automation: reading notebooks, adding sources, generating Studio outputs and creating new notebooks.

What does notebooklm need to run?

A browser automation environment — Claude CLI with computer-use, the Claude Chrome Extension, or Playwright/Puppeteer with screenshot and click tools. It won't run in Claude.ai web.

Source text

notebooklm · MIT
# notebooklm

Browser-automation skill for controlling Google's NotebookLM (https://notebooklm.google.com). The only **browser-automation shape** in the v2 collection — distinct from the research-pack convention.

## Critical Portability Notice

> **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.

This skill cannot run in Claude.ai web (no browser automation). It detects environment at Step 0 and exits cleanly if unsupported.

## What this skill does

Four core actions controlled via the grill-me action-routing intake:

| Action | Q1 picks | UI flow |
|---|---|---|
| **Read/Extract** | 1 | Ask the notebook's chat a question, return clean response |
| **Add Sources** | 2 | Push URL / text / file / Google Doc / synthesized content into a notebook |
| **Generate Studio Outputs** | 3 | Audio Overview, Study Guide, Briefing Doc, Timeline, FAQ, Table of Contents, Infographic, Slides, Mind Map |
| **Create New Notebook** | 4 | Initialize with title + initial sources |

## Domain folder — research (semantic) vs shape difference

This skill lives in `research/` (with pulse/litreview/grants/dossier/patent/syllabus) because its **user-facing semantic domain** is research — users automate NotebookLM as part of their research workflow.

But the **technical shape** is completely different from the research-pack:
- No Consensus / Agent Integrity Rules
- No 1 q/sec rate limits (browser automation has different constraints)
- No DOCX generation (NotebookLM outputs come from NotebookLM itself)
- No three-count tracking
- Async discipline is fundamentally different (UI generation can take 5-10 min)

Users find it where they expect (research/), but it's the only research-domain skill with this shape.

## Source spec

`megaprompts/03-notebooklm-megaprompt.md` (maintainer-local draft spec — gitignored, not in the public repo) (PR #657).

## Plugin layout

```
research/notebooklm/
├── .claude-plugin/plugin.json
├── README.md
├── agents/cs-notebooklm.md          ← browser-automation persona, async-discipline enforcer
├── commands/cs-notebooklm.md        ← /cs-notebooklm (or auto-triggers on phrases)
└── skills/notebooklm/
    ├── SKILL.md
    ├── references/
    │   ├── browser_automation_canon.md         ← screenshot-first / find-before-click (7+ sources)
    │   ├── studio_output_custom_prompts.md     ← why default prompts mediocre + per-type templates (7+ sources)
    │   └── async_action_discipline.md          ← fire-and-notify pattern for slow UI ops (7+ sources)
    └── scripts/
        ├── action_router.py                    ← stdlib: Q1-Q4 answers → action plan + UI flow
        ├── custom_prompt_template_generator.py ← stdlib: studio output type + audience → custom prompt starter
        └── async_action_classifier.py          ← stdlib: action → wait-or-notify-and-move-on
```

## Dependencies

- **Browser automation tool** — Required. Examples:
  - Claude Code CLI with computer-use
  - Claude Chrome Extension
  - Playwright / Puppeteer with screenshot + click tools
- **NotebookLM account** (Google) — User-provided, never auto-login

## License

MIT.

© Alireza Rezvani · MIT · alirezarezvani/claude-skills

Similar plugins

All plugins for Browser and scraping →

From the same set394

The whole set →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor