notebooklm-skill
notebooklm-skill bridges NotebookLM research with Claude-style content generation and distribution. It ingests URLs/PDFs/trending topics, creates and manages NotebookLM notebooks, runs deep research/QA with citations, generates multiple artifact types (text and downloadable assets like audio/video/slides/reports and some structured outputs), and can run as a CLI tool, a Claude Code Skill, or an MCP server for agent-driven workflows.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
The README emphasizes session storage for Google browser login (no API keys). However, it does not document transport security guarantees, fine-grained scopes/authorization boundaries, audit logging, or how secrets/tokens are handled within the MCP/CLI processes. Dependency security posture is not verifiable from the provided content; presence of Playwright/httpx suggests additional surface area.
⚡ Reliability
Best When
You want an agent-friendly research-and-content pipeline that can be driven programmatically (MCP) or from the command line, with Google-browser login already acceptable.
Avoid When
You need fine-grained authorization controls (scopes), strict error-code contracts, or strong operational guarantees like documented SLAs and robust retry/idempotency semantics.
Use Cases
- • Research-to-article pipelines from URLs, PDFs, and arXiv sources
- • Deep research Q&A with citations for drafting content
- • Trending-topic discovery followed by automated notebook research and content generation
- • Generating social posts/threads/newsletters from research outputs
- • Batch generation of learning artifacts (slides, podcasts, quizzes, flashcards, study guides, etc.)
- • Agent workflows via MCP tools (create/list/add-source/ask/summarize/generate/download/research/trend-research)
Not For
- • Purely offline or air-gapped usage (implied by web/PDF ingestion and upstream services)
- • Requirements for an official REST/GraphQL/SDK-based developer API (primarily CLI + MCP)
- • Use cases needing documented rate-limit headers/guarantees or a published SLA for uptime
- • Highly regulated environments that require explicit compliance and data-residency guarantees
Interface
Authentication
Authentication is described as browser-based Google login with stored session cookies/state for subsequent CLI/MCP calls. No API-key/OAuth client/explicit scopes are documented in the provided README.
Pricing
The provided material does not describe pricing tiers for notebooklm-skill itself; it appears to rely on upstream NotebookLM usage and Google login for access, but costs are not documented here.
Agent Metadata
Known Gotchas
- ⚠ Session-based Google login is required; expired sessions may cause auth errors until re-login
- ⚠ Infographic is listed as excluded from downloadable types (possible mismatch with agent expectations around downloadable artifacts)
- ⚠ Audio format is M4A (not MP3), which can break downstream media tooling if assumed otherwise
- ⚠ No explicit rate-limit or retry/backoff strategy is described in the provided README
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for notebooklm-skill.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.