notebooklm-connector
NewA plugin to manage NotebookLM notebooks and query them using integrated features.
Summary
This skill connects Claude Code to Google's NotebookLM, allowing you to manage notebooks, add or remove sources, and query your notebooks using natural language.
- It streamlines research workflows by letting you interact with your NotebookLM content directly from the terminal.
Overview
A plugin marketplace I built from what I needed while using Claude Code.
 
<div align="center">
<video src="https://github.com/user-attachments/assets/abb70886-6f82-474c-a956-3c89b77c4ae5" width="600" controls></video>
</div>
Install
Option A — Plugin Marketplace (recommended)
Full install: skills, hooks, agents, MCP servers, scripts — everything the plugin ships.
# 1. Add the marketplace (once)
/plugin marketplace add LeeJuOh/claude-code-zero
# 2. Install a plugin
/plugin install <plugin-name>@claude-code-zeroOr from the terminal:
claude plugin add <plugin-name>@claude-code-zeroOption B — npx skills (skills only)
Installs SKILL.md files via the skills CLI. Quick, no marketplace registration needed — but hooks, agents, MCP servers, and scripts are not included. Plugins that depend on hooks (worktree-plus, rubber-duck-tutor, claw-mo) or agents (vision-powers, codex-advisor) will have reduced functionality.
npx skills add LeeJuOh/claude-code-zeroVerify
Run /plugin and check the Installed tab.
Plugins
codex-advisor
Problem: Codex outputs look confident but hallucinate citations and miss edge cases. You won't catch it by reading alone.
Solution: Claude independently re-verifies every Codex response — without seeing source code until after Codex returns. Five-way classification (Agreed / Disputed / Nuanced / False Positive / Uncited) so you know exactly what to trust.
codex-review · codex-adversarial · codex-rescue · codex-verify · codex-research · codex-status · codex-result · codex-cancel · codex-setup
vision-powers
Problem: Complex analysis buried in terminal text — architecture, security issues, git diffs all lose structure. Impossible to share with teammates.
Solution: Generates interactive HTML reports with Mermaid diagrams and Chart.js dashboards. Analyzes plugins (local, installed, or GitHub), git diffs, and markdown docs. Visual self-audit renders reports to PNG for verification.
plugin-visual · diff-visual · doc-visual · fact-check · context-health-visual · report-manager
skill-creator-pro
Problem: Building a skill that triggers when it should and actually helps is trial and error — no way to measure trigger accuracy, no structured improvement loop, no benchmark to tell you if a change helped.
Solution: Anthropic's official skill-creator coaching loop — draft, test against real prompts, review side-by-side baseline-vs-with-skill diffs, improve — plus a description-trigger optimizer and an HTML benchmark viewer. auto-optimize adds a hands-off hill-climbing pass for skills that already mostly work.
skill-creator-pro · auto-optimize
worktree-plus
Problem: Claude Code's built-in worktree breaks on gitignored files (.env, node_modules/), doesn't track state, and can delete uncommitted work on removal.
Solution: .worktreeinclude / .worktreelink for selective file copy and symlink. Safety guard blocks removal if uncommitted changes or unpushed commits exist. Audit trail in .worktree.log.
worktree-config · auto-hooks on WorktreeCreate/Remove
notebooklm-connector
Problem: Your research lives in NotebookLM but querying it means context-switching, copy-pasting, and burning tokens on ungrounded answers.
Solution: Chrome automation queries NotebookLM directly from Claude Code. Source-grounded answers with automatic follow-up rounds (default 3) to fill coverage gaps. Per-project notebook registry.
notebooklm-manager (query · add · list · search · enable/disable · remove)
claw-mo
Problem: mo markdown viewer is powerful but tedious to configure — port numbers, watch patterns, fsnotify drops files silently.
Solution: Per-project config with auto-sync hook. Every time Claude writes or edits a markdown file, it appears in mo automatically. Group-based organization, full-text search, Mermaid + KaTeX + Shiki rendering.
claw-mo-setup · claw-mo-up · claw-mo-down · claw-mo-open · claw-mo-manage
claw-mux
Problem: Claude Code is trapped in a single terminal pane. Can't send commands to other panes, read their output, or orchestrate parallel workflows.
Solution: Full cmux integration — split layouts, send commands to any pane, read screen output, automate WKWebView browsers, and report progress via sidebar primitives (status / progress bar / leveled logs).
claw-mux · cmux-browser · cmux-markdown
toolbox
Problem: WebFetch gets blocked by bot detection. Session context vanishes between conversations. Secrets end up hardcoded. References drift out of sync.
Solution: Five focused utilities — Gemini fallback (auto-triggers on WebFetch failure), resumption-ordered handoff docs, secret extraction with auto-load hooks, sitemap discovery, and reference sync.
gemini-fetch · handoff · secret-setup · fetch-sitemap · sync-references
rubber-duck-tutor
Problem: Passively accepting AI-generated code leads to 17% worse comprehension. You merge code you don't truly understand.
Solution: Rubber duck questioning across 5 development phases — asks you to explain what the code does before you ship it. Hint ladder guides without revealing answers. Auto-suggests review at plan creation, PR, and git push.
duck · duck-design · duck-plan · duck-verify · duck-review · duck-orient
vibeproxy-kit
Problem: Wiring VibeProxy manually (OAuth, aliases, config.yaml, shell edits) is error-prone. State is unclear — which backend is actually responding?
Solution: Explicit state management with backup/rollback. Per-backend isolation probe tells you exactly which model handles each alias. Pre-existing alias migration with Keep / Merge / Reset modes.
setup-aliases · cc-list
Lab Plugins
Experimental. May require specific environments or have limited stability.
e2e-test-runner
Problem: E2E tests require brittle selectors and page objects. They break on every UI change and take forever to write.
Solution: Write tests in natural language JSON. Claude reads the page, decides what to click, and validates outcomes. Video recording per test, visual regression via pixel-diff, and auto-detects your dev server (Next / Vite / Remix / Astro / and more).
e2e-test
Plugin Management
/plugin disable <plugin-name>@claude-code-zero # Disable
/plugin enable <plugin-name>@claude-code-zero # Re-enable
/plugin update <plugin-name>@claude-code-zero # Update to latest
/plugin uninstall <plugin-name>@claude-code-zero # UninstallLicense
Install & Usage
/plugin marketplace add <org/repo>Add the configuration to /plugin install notebooklm-connector@<marketplace>
/pluginUse Cases
Usage Examples
/notebooklm-connector list notebooks
/notebooklm-connector query 'What are the key findings from my research notes?'
/notebooklm-connector add-source --notebook 'Project Alpha' --url 'https://example.com/report.pdf'
Security Audits
Frequently Asked Questions
What is notebooklm-connector?
This skill connects Claude Code to Google's NotebookLM, allowing you to manage notebooks, add or remove sources, and query your notebooks using natural language. It streamlines research workflows by letting you interact with your NotebookLM content directly from the terminal.
How to install notebooklm-connector?
To install notebooklm-connector: add a marketplace (/plugin marketplace add <org/repo>), then add the config to /plugin install notebooklm-connector@<marketplace>. Finally, /plugin in Claude Code.
What is notebooklm-connector best for?
notebooklm-connector is a plugin categorized under General. It is designed for: plugin. Created by LeeJuOh.
What can I use notebooklm-connector for?
notebooklm-connector is useful for: Query a NotebookLM notebook to retrieve specific information from your sources.; Add new sources (e.g., web links, PDFs, Google Docs) to an existing notebook.; List all your NotebookLM notebooks and their metadata.; Create a new notebook and populate it with relevant sources for a project.; Remove outdated or irrelevant sources from a notebook.; Search across multiple notebooks for a topic using integrated queries..