How do I install the Notebooklm skill?

Run npx skillmds@latest add tomevault-io/notebooklm-6 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Notebooklm safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Notebooklm?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Notebooklm free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Notebooklm?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Notebooklm by tomevault-io — Agent Skill

Name: Notebooklm
Author: tomevault-io

Notebooklm

Use this skill when the user wants to interact with Google NotebookLM (notebooklm.google.com). Triggers on requests to query notebooks, search documents, add sources (URLs, GDrive, PDFs), generate audio podcasts/videos from documents, share notebooks, or manage the NotebookLM library. Use this skill for source-grounded answers without hallucination.

tomevault-io Updated Sep 17, 2026

File contents

NotebookLM Assistant Skill

You have native Model Context Protocol (MCP) tools available to interact directly with the user's Google NotebookLM account. There is no need to run local python scripts or launch browsers manually—the notebooklm-mcp server handles everything natively.

Workflow

Verify Connection: You should already have access to tools starting with notebook_, source_, research_, studio_, etc. If any of these throw an authentication error (401 Unauthorized, Invalid CSRF), prompt the user to open their terminal and run nlm login to re-authenticate. DO NOT try to fix auth yourself.
Understand the Goal: Identify what the user wants to do: query an existing notebook, add sources, or generate artifacts (like audio overviews).
Execute via Native Tools: Call the appropriate MCP tools directly.

Detailed Tool Usage

To avoid cluttering your context, detailed lists of tools and their specific parameters have been moved to reference files. Read these only when you need them.

Available Tools & Capabilities: Read references/mcp_tools.md for a complete mapping of all 29 tools available to you (CRUD for notebooks, sources, notes, sharing, and studio artifacts). This includes important warnings about operations that require confirm=True.
Query Best Practices: Read references/best_practices.md if the user wants you to ask a question to a notebook via notebook_query. It contains critical instructions on how to handle NotebookLM's grounded responses and when to ask follow-up questions to synthesize a complete answer.

Key Principles

Confirmation Required: Destructive actions (notebook_delete, source_delete) and generative actions (studio_create, source_sync_drive) require you to pass confirm=True. You must get explicit user consent before doing this.
Asynchronous Work: Actions like research_start and studio_create run in the background. You must poll research_status or studio_status to determine when they are complete.
Follow-ups Are Mandatory: When using notebook_query, NotebookLM may provide truncated or narrowly-focused answers based only on the sources. Check if "Is that ALL you need to know?" applies, and proactively query again to fill gaps before answering the user.

Important Note

This skill replaces the legacy Python-based run.py wrapper. If you see old references to scripts/run.py or auth_manager.py in your history, ignore them. You are dealing with native MCP tools now.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: notebooklm-6description: Use this skill when the user wants to interact with Google NotebookLM (notebooklm.google.com). Triggers on requests to query notebooks, search documents, add sources (URLs, GDrive, PDFs), generate audio podcasts/videos from documents, share notebooks, or manage the NotebookLM library. Use this skill for source-grounded answers without hallucination.---# NotebookLM Assistant SkillYou have native Model Context Protocol (MCP) tools available to interact directly with the user's Google NotebookLM account. There is no need to run local python scripts or launch browsers manually—the `notebooklm-mcp` server handles everything natively.## Workflow1. **Verify Connection**: You should already have access to tools starting with `notebook_`, `source_`, `research_`, `studio_`, etc. If any of these throw an authentication error (`401 Unauthorized`, `Invalid CSRF`), prompt the user to open their terminal and run `nlm login` to re-authenticate. DO NOT try to fix auth yourself.2. **Understand the Goal**: Identify what the user wants to do: query an existing notebook, add sources, or generate artifacts (like audio overviews).3. **Execute via Native Tools**: Call the appropriate MCP tools directly.## Detailed Tool UsageTo avoid cluttering your context, detailed lists of tools and their specific parameters have been moved to reference files. Read these **only** when you need them.- **Available Tools & Capabilities**: Read `references/mcp_tools.md` for a complete mapping of all 29 tools available to you (CRUD for notebooks, sources, notes, sharing, and studio artifacts). This includes important warnings about operations that require `confirm=True`.- **Query Best Practices**: Read `references/best_practices.md` if the user wants you to ask a question to a notebook via `notebook_query`. It contains critical instructions on how to handle NotebookLM's grounded responses and when to ask follow-up questions to synthesize a complete answer.## Key Principles- **Confirmation Required**: Destructive actions (`notebook_delete`, `source_delete`) and generative actions (`studio_create`, `source_sync_drive`) require you to pass `confirm=True`. You must get explicit user consent before doing this.- **Asynchronous Work**: Actions like `research_start` and `studio_create` run in the background. You must poll `research_status` or `studio_status` to determine when they are complete.- **Follow-ups Are Mandatory**: When using `notebook_query`, NotebookLM may provide truncated or narrowly-focused answers based *only* on the sources. Check if "Is that ALL you need to know?" applies, and proactively query again to fill gaps before answering the user.## Important NoteThis skill replaces the legacy Python-based `run.py` wrapper. If you see old references to `scripts/run.py` or `auth_manager.py` in your history, ignore them. You are dealing with native MCP tools now.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/pablodiegoo) — claim your Tome and manage your conversions.

Frequently asked questions