From notebooklm-enhanced
Ask questions to NotebookLM about your notebook sources — supports citations, follow-ups, and source filtering
How this command is triggered — by the user, by Claude, or both
Slash command
/notebooklm-enhanced:queryThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Query NotebookLM Ask a question against notebook sources and get an AI-generated answer with citations. ## Arguments Parse from: `$ARGUMENTS` Required: - Question text (the main argument) Options: - `--notebook <id>`: Target a specific notebook (otherwise uses active notebook) - `--source <id>`: Limit query to specific source(s) — can be repeated - `--follow-up` or `-c <conversation_id>`: Continue an existing conversation - `--save`: Save the answer as a note in the notebook ## Workflow 1. **Parse arguments**: Extract the question, optional notebook ID, source IDs, and conversation...
Ask a question against notebook sources and get an AI-generated answer with citations.
Parse from: $ARGUMENTS
Required:
Options:
--notebook <id>: Target a specific notebook (otherwise uses active notebook)--source <id>: Limit query to specific source(s) — can be repeated--follow-up or -c <conversation_id>: Continue an existing conversation--save: Save the answer as a note in the notebookParse arguments: Extract the question, optional notebook ID, source IDs, and conversation ID.
Verify context (if no --notebook specified):
uv run --project "${CLAUDE_PLUGIN_ROOT}/scripts" notebooklm status
Ensure there is an active notebook. If not, suggest running /notebooklm-enhanced:library first.
Run the query:
# Basic query
uv run --project "${CLAUDE_PLUGIN_ROOT}/scripts" notebooklm ask "YOUR QUESTION HERE" --json
# With specific sources
uv run --project "${CLAUDE_PLUGIN_ROOT}/scripts" notebooklm ask "YOUR QUESTION" -s SOURCE_ID_1 -s SOURCE_ID_2 --json
# Follow-up in existing conversation
uv run --project "${CLAUDE_PLUGIN_ROOT}/scripts" notebooklm ask "FOLLOW UP QUESTION" -c CONVERSATION_ID --json
# With explicit notebook
uv run --project "${CLAUDE_PLUGIN_ROOT}/scripts" notebooklm ask "YOUR QUESTION" --notebook NOTEBOOK_ID --json
Parse JSON response: The output contains:
{
"answer": "The answer text with [1] [2] citation markers...",
"conversation_id": "...",
"turn_number": 1,
"is_follow_up": false,
"references": [
{"source_id": "...", "citation_number": 1, "cited_text": "..."},
{"source_id": "...", "citation_number": 2, "cited_text": "..."}
]
}
Format output: Present the answer with properly formatted citations. For each reference, show the citation number and the relevant quoted text.
Report conversation ID: Always include the conversation_id so the user can run follow-up queries with -c.
/notebooklm-enhanced:query What are the main findings of this paper?
/notebooklm-enhanced:query --notebook abc123 What methods were used?
/notebooklm-enhanced:query --source def456 Summarize this source
/notebooklm-enhanced:query -c conv789 Can you elaborate on point 3?
--json flag on all ask commands to get structured output with citations.conversation_id enables multi-turn conversations — always surface it to the user.npx claudepluginhub fakoli/fakoli-plugins --plugin notebooklm-enhanced/askAsks NotebookLM a question about the current notebook's content via `notebooklm ask` CLI, displaying the response with optional source references via --json.
/nlmQuery NotebookLM notebooks for source-grounded, citation-backed answers from Gemini. Also supports listing, creating, renaming, deleting notebooks and managing sources.
/notebook-auditVerifies [NB##:K##] claim references in prose against notebook sources, surfacing unresolved or stale numeric references.
/brainLoads relevant notes from your Obsidian vault matching the topic into conversation context. Lists found notes and answers using their content.
/searchSearches Obsidian vault using qmd semantic search (BM25 + vectors + reranking), showing top 10 results with relevance scores, titles, paths, and snippets.
/queryQueries compiled wiki for answers using quick (indexes), standard (articles), or deep (full+raw+sibling) depths, citing sources only from wiki content.