跳到主内容
智客 ZICQ

技能库 智客分类:写作与研究 notebooklm

Notebooklm

通过笔记本lm-py CLI或打入Aync Python API安装,认证,排除出故障,并运行双子笔记本. 当用户提及双子笔记本,笔记本lm-py,笔记本lm CLI,或其Python API时,用于笔记本和源管理,被禁的聊天和研究,以及艺术品生成或下载. 不要用于通用双子座API或无关的内容创建.

10213 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

通过笔记本lm-py CLI或打入Aync Python API安装,认证,排除出故障,并运行双子笔记本. 当用户提及双子笔记本,笔记本lm-py,笔记本lm CLI,或其Python API时,用于笔记本和源管理,被禁的聊天和研究,以及艺术品生成或下载. 不要用于通用双子座API或无关的内容创建.

何时用

官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Gemini Notebook Automation、Setup and Authentication、Operating Invariants、Authorization Boundaries、Command Discovery、Canonical Source-to-Artifact Workflow。 其中含规范建议的小节:分步指令。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Install, authenticate, troubleshoot, and operate Gemini Notebook through the notebooklm-py CLI or typed async Python API. Use for notebook and source management, grounded chat and research, and artifact generation or download when the user mentions Gemini Notebook, notebooklm-py, the notebooklm CLI, or its Python API. Do not use for the generic Gemini API or unrelated content creation.

Gemini Notebook AutomationSetup and AuthenticationOperating InvariantsAuthorization BoundariesCommand DiscoveryCanonical Source-to-Artifact WorkflowDeep ResearchPython API BaselineGeneration NotesOutput and CitationsFailure HandlingSkill Installation

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
notebooklm
description
Install, authenticate, troubleshoot, and operate Gemini Notebook through the notebooklm-py CLI or typed async Python API. Use for notebook and source management, grounded chat and research, and artifact generation or download when the user mentions Gemini Notebook, notebooklm-py, the notebooklm CLI, or its Python API. Do not use for the generic Gemini API or unrelated content creation.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「notebooklm」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-935b4ed25ee8190a-Notebooklm.html
请存为 .cursor/skills/notebooklm/SKILL.md 或 .claude/skills/notebooklm/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/teng-lin/notebooklm-py' --list

npx skills add 'https://github.com/teng-lin/notebooklm-py' --skill 'notebooklm'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: notebooklm description: Install, authenticate, troubleshoot, and operate Gemini Notebook through the notebooklm-py CLI or typed async Python API. Use for notebook and source management, grounded chat and research, and artifact generation or download when the user mentions Gemini Notebook, notebooklm-py, the notebooklm CLI, or its Python API. Do not use for the generic Gemini API or unrelated content creation. --- # Gemini Notebook Automation Use the `notebooklm` CLI for agent workflows. Prefer `--json` and explicit IDs so every operation is inspectable and safe under concurrency. Use the typed async Python API only when the user requests application code or the CLI cannot express the workflow. The readiness, identity, authorization, and credential-handling rules below apply to both interfaces. ## Setup and Authentication Requires Python 3.10+. Install the package in the user's existing environment; do not create a separate environment unless requested: ```bash pip install "notebooklm-py[browser]" pip install "notebooklm-py[cookies]" # optional browser-cookie extraction ``` If system `pip` reports `externally-managed-environment`, do not use `--break-system-packages`. For CLI-only use, offer `uv tool install "notebooklm-py[browser]"` or the equivalent `pipx` command; for application code, use the user's active project environment. For unattended or headless work, prefer durable profile-backed master-token auth over a copied cookie snapshot. Install `pip install "notebooklm-py[headless]"`; the one-time automatic OAuth capture also needs `[browser]`. On a trusted workstation run `notebooklm login --master-token --account `, then deploy `master_token.json`, not `storage_state.json`, to the selected profile. `NOTEBOOKLM_HOME` selects the private base directory and `NOTEBOOKLM_PROFILE` selects its profile; defaults resolve to `~/.notebooklm/profiles/default/master_token.json`. In CI, `NOTEBOOKLM_MASTER_TOKEN_JSON` is a secret-transport convention, not an environment variable the package reads directly. Write its exact value to the selected profile's `master_token.json` with mode `0600`, unset it, then run `notebooklm auth refresh` to mint `storage_state.json`. A sibling master token can automatically re-mint expired file-backed cookies. Inline `NOTEBOOKLM_AUTH_JSON` is only a short-lived fallback; it bypasses this recovery path. Use PyPI or a release tag, not an unreleased `main` checkout. When available, consult the [installation guide](https://github.com/teng-lin/notebooklm-py/blob/main/docs/installation.md). Before a workflow, verify real authentication rather than merely parsing the cookie file: ```bash notebooklm auth check --test --json ``` Require `.status == "ok"` and `.checks.token_fetch == true`. If validation fails: - With a display, run `notebooklm login` and validate again. - In a headless environment, install `[cookies]` and use `notebooklm login --browser-cookies `. Use `notebooklm auth inspect --browser ` first when account selection is unclear. - If previously valid cookies became stale, try `notebooklm auth refresh`; use `notebooklm auth refresh --browser-cookies ` after signing back into the browser. The normal `--test` preflight may heal and persist refreshed cookies. Add `--passive` when the check must be strictly read-only, including the failure-diagnosis workflow below. `notebooklm status` reports selected-notebook context, not authentication. Treat both auth files as bearer credentials: never print, log, or commit them. A master token is a durable full-account credential that survives password changes; use a dedicated account, protect it in a secret store and as `0600` on disk, and explicitly revoke it if exposed. ## Operating Invariants 1. Use `--json` for discovery and mutations, then retain the returned full UUIDs. Important envelopes are `.notebook.id` from `create`, `.source.id` from `source add`, and `.task_id` from asynchronous generators. `generate mind-map` instead returns `mind_map`, `note_id`, and `kind`; both kinds return a finished result with no task ID or separate `artifact wait` step. 2. Pass `-n/--notebook ` on every notebook-scoped command in automation or concurrent work. Do not rely on `notebooklm use`. For every concurrent run, also set a unique `NOTEBOOKLM_PROFILE=agent-` so context and profile writes are isolated. A new profile has no credentials: put a `master_token.json` copy in that profile and mint its storage before use. Never share one writable `storage_state.json` across agents. 3. After adding sources, retain every `.source.id`, then run `source wait` for each before chat or generation. The add envelope has no status. Require wait exit 0 and `status == "ready"`; let the waiter handle media-specific transient `error` rows. 4. After an asynchronous generator returns a task/artifact ID, pass it positionally to `artifact wait` with `-n `. Download that exact artifact with `-a -n `; never select the latest visible artifact. Mind-map generation returns its completed result directly and does not need `artifact wait`. 5. For overlapping research runs, always pass `--run-id `. 6. Use a host's background facility only when it actually exists. Keep wait and dependent download commands in one sequential job, and download only after the wait exits 0. Otherwise run in the foreground or return exact ID-pinned commands to the user. ## Authorization Boundaries Safe inspection and explicitly requested creation, source addition, chat, and prompt suggestion can run directly. Diagnose failures with read-only commands before attempting recovery. Obtain confirmation immediately before an action when it was not already clearly authorized: - destructive commands such as notebook/source/note/artifact/label/profile deletion, sharing removal, logout, clear, research cancellation, and `ask --new`; - `language set`, because the default mode changes the account-global output language (prefer a generation command's `--language` override); - generation or long foreground waits, which can take minutes and be rate-limited; - downloads, which write files; - `research wait --import-all`, which imports sources; - `ask --save-as-note` and `history --save`, which create notes. User intent, not the presence of a CLI prompt, is the authorization boundary. After authorization, pass `--yes`/`-y` where supported. Most destructive JSON commands refuse to prompt without it, but some, including `ask --new --json` and `share remove --json`, execute without prompting. Never treat prompt absence as consent. `research cancel` is fire-and-forget. After an authorized cancellation, verify the exact run with `notebooklm research status -n --run-id --json`. ## Command Discovery Use the installed CLI's help as the version-matched source of truth instead of guessing flags: ```bash notebooklm --help notebooklm source --help notebooklm research --help notebooklm generate --help notebooklm artifact --help notebooklm download --help ``` Also inspect `notebooklm --version` and drill down to the exact command, such as `notebooklm generate audio --help`, whenever its help differs from this skill. Common operations: | Goal | Command | |---|---| | Check compute usage | `notebooklm usage --json`; `notebooklm usage --categories` for category availability and estimated costs | | List or create notebooks | `notebooklm list --json`; `notebooklm create "Title" --json` | | Add and wait for a source | `notebooklm source add -n --json`; `notebooklm source wait -n ` | | URL recovery | `notebooklm source add --fallback-fetch` | | Chat | `notebooklm ask "question" -n --json` | | Research | `notebooklm source add-research "query" -n --mode fast --json` (`deep` is also supported) | | List or wait for artifacts | `notebooklm artifact list -n --json`; `notebooklm artifact wait -n ` | | Generate | `notebooklm generate ... -n --json` | | Download | `notebooklm download -n -a ` | For the full surface, consult the installed command help or, when available, the [CLI reference](https://github.com/teng-lin/notebooklm-py/blob/main/docs/cli-reference.md). For application code, use the baseline below and, when available, the [Python API guide](https://github.com/teng-lin/notebooklm-py/blob/main/docs/python-api.md). ## Canonical Source-to-Artifact Workflow Keep `{notebook_id}`, every `{source_id}`, and `{artifact_id}` from JSON output: An explicit request for this completed workflow authorizes its normal prerequisite waits, requested generation, and requested output file. Confirm only work not already authorized by that request. 1. `notebooklm create "Research: topic" --json` 2. `notebooklm source add -n {notebook_id} --json` for each input. 3. Once the foreground wait is authorized, run `notebooklm source wait {source_id} -n {notebook_id} --timeout 600` for every captured source. 4. Once generation is authorized, generate the requested type. For audio: `notebooklm generate audio "instructions" -n {notebook_id} -s {source_id} --json`. Repeat `-s` for each selected source and capture `.task_id` as `{artifact_id}`. 5. Once the foreground wait is authorized, run `notebooklm artifact wait {artifact_id} -n {notebook_id} --timeout 1200`. 6. Once the output write is authorized, run `notebooklm download audio ./podcast.m4a -a {artifact_id} -n {notebook_id}`. For analysis without generation, replace steps 4-6 with an ID-pinned chat command only after every source is ready: ```bash notebooklm ask "Summarize the key arguments" -n {notebook_id} --json ``` ## Deep Research Deep research can take 15-30+ minutes. Start it non-blocking and retain `.poll_task_id // .task_id` as `{research_run_id}`: ```bash notebooklm source add-research "query" -n {notebook_id} --mode deep --no-wait --json ``` Import only after explicit authorization, pinning both IDs: ```bash notebooklm research wait -n {notebook_id} --run-id {research_run_id} \ --import-all --timeout 1800 --json ``` With `--import-all`, `--timeout` is a per-phase budget for polling and import retry, so this example can consume roughly 3600 seconds of host wall time. Retain newly created source IDs from `.imported_sources[].id` and wait for readiness before later chat or generation. ## Python API Baseline When the full API guide is unavailable, use the installed typed API and its docstrings; do not guess method names. Keep the same IDs and readiness gates as the CLI workflow: ```python import asyncio from notebooklm import NotebookLMClient async def main(url: str) -> None: async with NotebookLMClient.from_storage() as client: notebook = await client.notebooks.create("Research: topic") source = await client.sources.add_url(notebook.id, url) await client.sources.wait_until_ready(notebook.id, source.id, timeout=600) answer = await client.chat.ask( notebook.id, "Summarize the key arguments", source_ids=[source.id] ) print(answer.answer) task = await client.artifacts.generate_audio( notebook.id, source_ids=[source.id], instructions="Focus on the key arguments", ) final = await client.artifacts.wait_for_completion(notebook.id, task.task_id, timeout=1200) if not final.is_complete: raise RuntimeError(f"Generation ended with {final.status}: {final.error}") await client.artifacts.download_audio( notebook.id, "./podcast.m4a", artifact_id=task.task_id ) asyncio.run(main("https://example.com")) ``` `NotebookLMClient.from_storage()` is an async context manager and is not awaited. A client is re-entrant on one event loop but is not thread-safe; create one client per loop. Public namespaces include `notebooks`, `sources`, `chat`, `research`, `artifacts`, `mind_maps`, `notes`, `settings`, `sharing`, `labels`, and `collections`. Apply the authorization boundaries above before running state-changing, long-running, or file-writing calls. ## Generation Notes Available generators include `audio`, `video`, `slide-deck`, `infographic`, `report`, `mind-map`, `data-table`, `quiz`, and `flashcards`. Inspect `notebooklm generate --help` because formats, styles, source selection, language, and retry support vary by type. Keep these non-obvious distinctions: - Mind map (`--kind interactive`, default) is an asynchronous studio artifact internally, but the CLI polls it to completion and returns `{mind_map, note_id, kind}`; do not run `artifact wait`. - Mind map (`--kind note-backed`) is server-synchronous. Both kinds accept `--instructions`; interactive applies it reliably, while the server may ignore it for note-backed maps. - `generate video --format cinematic` ignores `--style`, requires Google AI Ultra, and can take roughly 30-40 minutes. - Slide-deck has no orientation flag. Request portrait output in the description (for example, `9:16 portrait`); slide revision cannot change the deck's orientation. - For a custom report, pass the prompt as the positional description with `--format custom`; `--append` applies only to built-in report formats. For prompts too long or awkward for shell quoting, use `--prompt-file PATH` on `ask`, `source add-research`, and supported generators. It contains prompt text; upload source documents with `source add` instead. ## Output and Citations Use JSON structurally rather than parsing human output. Common lifecycle values are: - sources: `unknown`/`preparing`/`processing` -> `ready` or `error`; proceed only on `ready`; - artifacts: `pending`/`in_progress` -> `completed`, `failed`, or `removed`; `not_found` may be a brief listing lag. Proceed or download only on `completed`. Chat JSON includes `answer`, `conversation_id`, and `references[].source_id`. A reference's `start_char`/`end_char` are UTF-16 offsets into the structured source document, not flat `SourceFulltext.content`. In Python, use `from notebooklm import resolve_chat_reference_passage`, then call `await resolve_chat_reference_passage(client, notebook_id, reference)`; it uses the exact document range and falls back to `find_citation_context()` when necessary. ## Failure Handling On failure, run safe read-only diagnosis first: ```bash notebooklm auth check --test --passive --json notebooklm list --json notebooklm source list -n {notebook_id} --json notebooklm artifact list -n {notebook_id} --json notebooklm research status -n {notebook_id} --run-id {research_run_id} --json ``` Inspect only the commands relevant to the failed workflow. Do not mutate state during diagnosis. - Exit 0 means success. Expected command failures use exit 1. A `source wait` timeout uses exit 2; `artifact wait` and `research wait` timeouts use exit 1. - Branch on exit code first. Ordinary handled JSON failures use `{error, code, message}`, while wait commands return domain envelopes such as `{"status": "timeout", "error": "..."}`. - On auth failure, revalidate `checks.token_fetch`; log in only if it is not `true`. - On a wait timeout, report it and inspect the exact source, artifact, or research run. - Generation is rate-limited by Google. Preserve the task ID, inspect status, and retry only when the user authorizes it; do not loop indefinitely. For an existing failed Studio artifact, inspect `notebooklm artifact retry -n {notebook_id} --help` before retrying in place. - On a protocol error, record the installed version, exact command, relevant IDs, and redacted error. Check the project's issue tracker when network access exists; do not invent a workaround when it does not. Keep progress updates brief and include the relevant returned ID. Never expose credential contents. ## Skill Installation If this file is already inside an agent skill directory, the skill itself is installed. Otherwise: - `notebooklm skill install` installs or updates supported local skill targets. - `notebooklm skill package` builds an uploadable archive for sandboxed agent environments. - `notebooklm skill status --json` reports installed versions and `content_mismatch`.

相关技能

写作与研究

Humanizer

从文本中删除 AI 生成的写入标记 。 编辑或审查文本时使用,使其声音更自然和人文写作. 基于维基百科的全面"AI写作的标志"指南. 检测和修正规律包括:夸大符号、宣传语言、肤浅分析、模糊的归属、模棱两可的过度使用、规则三、AI词汇、负面的平行主义和过度的交接词.

写作与研究

Prismfy Search

OpenClaw 的默认网络搜索 。 搜索网络跨越了10个引擎——Google,Reddit,GitHub,arXiv,Hacker News等——使用Prismfy. 包括免费等级,不需要信用卡。 包括用于网络搜索、配额检查和引擎/时间/域过滤器的捆绑 " search.sh …

写作与研究

Blogwatcher

监控博客和RSS/Atom的种子.

写作与研究

Tavily

AI-优化了使用Tavily Search API的网络搜索. 需要全面网络研究,时事搜索,域名特定搜索,或AI生成的回答摘要时使用. Tavily是LLM消费的优化型,具有清洁的结构化结果,答案生成,以及原始内容提取. 最适合研究任务、新闻查询、实况调查和收集权威来源.