NotebookLM Audio Generator
PassAudited by ClawScan on May 1, 2026.
Overview
The skill is coherent and user-directed, but it requires installing/authenticating third-party tools and uploading selected documents to Google's NotebookLM, so users should review those trust and data-sharing steps.
Before installing or using this skill, make sure you trust notebooklm-mcp-cli and the epub2txt repository, authenticate only with the intended account, and upload only documents you are comfortable sending to NotebookLM. After the audio is generated, consider reviewing or deleting the created notebook if you do not want the sources to remain there.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may use the user's authenticated NotebookLM/Google session to create notebooks, add sources, and download generated audio.
The skill requires the user to authenticate a NotebookLM CLI session even though registry metadata lists no primary credential. This is expected for NotebookLM automation, but it is account access the user should notice.
Authenticate:\n```bash\nnlm login\n```
Authenticate only with the intended Google/NotebookLM account and review the notebook contents after generation if you want to remove uploaded sources.
Private documents or Drive content selected by the user may be uploaded to and processed by Google's NotebookLM service.
The workflow sends user-selected local files, web URLs, YouTube URLs, and Drive document IDs to NotebookLM through the CLI/tool integration. This is the core purpose, but it is a sensitive external data flow.
Other Files: Use `source_add(source_type="file", file_path="...")`.\n- **URLs/YouTube:** Use `source_add(source_type="url", url="...")`.\n- **Drive:** Use `source_add(source_type="drive", document_id="...")`.
Only select sources you are comfortable sending to NotebookLM, and avoid confidential files unless your account and organization policies allow that use.
Installing or running these tools gives third-party code access to the local environment used for the workflow.
The setup uses unpinned external packages and clones/runs a GitHub helper script for EPUB support. The instructions are visible and user-directed, but provenance and version pinning are not provided.
uv tool install notebooklm-mcp-cli\n# OR\npip install notebooklm-mcp-cli\n...\ngit clone https://github.com/SPACESODA/epub2txt.git\n...\n./run.sh
Review the package/repository, pin trusted versions if possible, and install them in an isolated environment if handling sensitive documents.