skills/notebooklm-consult/SKILL.md
# NotebookLM Consult Connect to an existing NotebookLM notebook and consult it on specific topics — ask questions, get grounded answers with citations, and optionally generate artifacts. ## Trigger When the user asks to consult a notebook, query NotebookLM, ask a question to their research, look something up in their notes, or references a specific NotebookLM notebook by name or ID. ## Prerequisites - `notebooklm` CLI installed (`pipx install "notebooklm-py[browser]"`) - Authenticated: `not
npx skillsauth add razbakov/skills skills/notebooklm-consultInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Connect to an existing NotebookLM notebook and consult it on specific topics — ask questions, get grounded answers with citations, and optionally generate artifacts.
When the user asks to consult a notebook, query NotebookLM, ask a question to their research, look something up in their notes, or references a specific NotebookLM notebook by name or ID.
notebooklm CLI installed (pipx install "notebooklm-py[browser]")notebooklm login (one-time browser auth)List available notebooks and match by name or ID:
notebooklm list
If the user specified a notebook name, match it from the list. If ambiguous, show options and ask. Once identified:
notebooklm use <notebook_id>
If no notebook is specified, show the list and ask the user to pick one.
Get a summary and source list to understand what content is available:
notebooklm summary --topics
notebooklm source list
Share a brief overview with the user: notebook title, number of sources, and suggested topics.
If the user wants a specific consultation style, configure the chat mode:
# For learning/educational queries
notebooklm configure --mode learning-guide
# For quick answers
notebooklm configure --mode concise
# For deep analysis
notebooklm configure --mode detailed
# For custom expert persona
notebooklm configure --persona "Act as a ${DOMAIN} expert consultant"
Default: skip this step (uses notebook's existing configuration).
Query the notebook with the user's questions:
notebooklm ask "What does the research say about ${TOPIC}?"
For follow-up questions in the same conversation context, just keep asking:
notebooklm ask "Can you elaborate on that second point?"
To focus on specific sources within the notebook:
# First check source IDs
notebooklm source list --json
# Then query specific sources
notebooklm ask -s <source_id> -s <source_id> "Compare these two perspectives on ${TOPIC}"
For structured output with citation references:
notebooklm ask "${QUESTION}" --json
To save an important answer as a note inside the notebook:
notebooklm ask "${QUESTION}" --save-as-note --note-title "Key findings on ${TOPIC}"
For deeper exploration, chain questions logically:
If the user wants deliverables from the consultation:
# Study guide summarizing the consultation topic
notebooklm generate report --style study-guide --wait
# Quiz to test understanding
notebooklm generate quiz --difficulty medium
# Audio summary for later listening
notebooklm generate audio "Focus on ${TOPIC}" --wait
notebooklm download audio ./consult-${TOPIC}.mp3
# Mind map of concepts
notebooklm generate mind-map --wait
# View full Q&A history
notebooklm history --show-all
# Save as a note for future reference
notebooklm history --save --note-title "Consultation: ${TOPIC} - $(date +%Y-%m-%d)"
--json flag on ask to get structured output with source references for programmatic use-s flag to scope questions to specific sources when the notebook has manynotebooklm logindevelopment
Seed a new or empty Instagram account with a 9-post grid (3×3) so the profile looks established the moment a new visitor lands. Designed for festivals, new businesses, product launches, conferences, communities — any time an empty IG profile would hurt conversion from external traffic (QR scans, flyer drops, cross-promo). Generates assets via /image-from-gemini (per content-publishing rules — never HTML), writes captions with hashtag sets, and outputs a posting order + cadence plan. Trigger generously: phrases like '9 posts for instagram', 'fill my IG', 'starter grid', 'launch grid', 'instagram seed', '9-post grid', 'IG account not to look empty', 'first instagram posts', 'feed bootstrap', '3x3 grid', 'instagram launch content'. Even if the user mentions only one piece (just the images, just the captions, just the order), use this skill — the grid only works as an integrated bundle.
testing
Translate one English blog post into multiple target languages via parallel sub-agents, preserving frontmatter conventions, hero image, and brand voice. Use when the user shares a published English post URL or markdown path and says 'translate it', 'add other languages', 'publish in DE/ES/RU/UK', 'translate to 5 languages', or asks for localized versions of a specific post.
development
Build a complete press kit for an event, product launch, or campaign — in multiple languages — and publish it as a shareable Google Drive folder ready to send to journalists, partners, or a delegate. Produces press releases (typically DE/EN/ES, or configurable), uploads press photos and flyers, creates an Overview document for at-a-glance briefing, and creates a Handover document with pending tasks, contacts, risks, and decisions so press distribution can be delegated. Use when the user says 'I need a press release', 'create a press kit', 'press release in X languages', 'set up a Drive folder for press', 'handover doc for someone else to run press', or has an upcoming announcement that needs to be sent to media. Trigger generously: even partial requests (just a press release, just a flyer folder) typically evolve into the full kit.
development
Track ticket sales for a live event (concert, festival, conference, workshop) with daily snapshots, generate a burndown chart comparing actual sales to ideal-linear targets and tier-cumulative milestones, and report whether the event is on pace. Use when the user asks how sales are going, wants to know if their event will sell out, asks for a daily sales report, wants to set up sales tracking for an upcoming event, or asks about ticket pace / velocity / projection. Trigger generously: phrases like 'how is concert sales going', 'burndown for my event', 'are we going to sell out', 'sales velocity', 'daily ticket chart', 'how many tickets do we need to sell', or any case where the user has a ticketed event with a fixed sales window and wants visibility on pacing.