Skip to main content
ClaudeWave
ES, Spanish
Skill32.8k estrellas del repoactualizado 6d ago

deep-research-notebooklm

# Deep Research via NotebookLM This Claude Code skill conducts structured multi-source research on topics including market analysis, competitive intelligence, trend analysis, and prospect research using Google NotebookLM's research engine. Use it when you need comprehensive, formatted research briefs with optional studio artifacts like slides, podcasts, videos, infographics, reports, or mind maps, and have NotebookLM MCP server configured and running.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/davila7/claude-code-templates /tmp/deep-research-notebooklm && cp -r /tmp/deep-research-notebooklm/cli-tool/components/skills/ai-research/deep-research-notebooklm ~/.claude/skills/deep-research-notebooklm
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Deep Research via NotebookLM

Research **$ARGUMENTS** deeply using the NotebookLM MCP server and deliver a structured research brief. Optionally generate studio artifacts (slides, audio podcasts, videos, infographics, reports, mind maps) from the research.

## Prerequisites

- **NotebookLM MCP server** must be configured. Install via: `nlm setup add claude-code`
- If NotebookLM MCP tools are not available, tell the user to run the setup command and restart their session.

## Research Workflow

### Step 1: Define Scope

Determine the **research type** based on the user's request:

| Type | Focus |
|------|-------|
| **Market Research** | Industry trends, market sizing, opportunities, TAM/SAM/SOM |
| **Competitive Intel** | Competitor analysis, positioning gaps, feature comparisons |
| **Client/Prospect Research** | Company background, pain points, decision makers, recent news |
| **Trend Analysis** | Technology trends, adoption patterns, forecasts, emerging players |
| **Proposal Research** | Background for proposals, sector-specific data, case studies |
| **Academic/Technical** | Papers, frameworks, methodologies, state of the art |

Tell the user what you plan to research and confirm the angle:

> "I'll research [topic]. My angle: [specific focus]. I'll investigate: [2-3 specific questions]. Sound right, or should I adjust?"

Wait for confirmation before proceeding.

### Step 2: Create NotebookLM Notebook

Use `notebook_create` to create a notebook named:
`Research: [Topic] - [YYYY-MM-DD]`

### Step 3: Add Context Sources

Use `source_add` to seed the notebook with relevant context:
- Add any URLs the user provides (articles, company pages, reports)
- Add any documents or files the user references
- Add text summaries of relevant background if no URLs are available
- If researching a company, add their website, LinkedIn, recent press

### Step 4: Run Research

Use `research_start` with a well-crafted query based on the topic and context.

**Mode selection:**
- Default: `"fast"` (~60 seconds, ~10 sources) -- good for most queries
- Use `"deep"` only if the user explicitly asks for exhaustive research (can take 10+ minutes and may stall at 0 sources)

**Tip:** Run direct `WebSearch` calls in parallel with NotebookLM for faster initial data gathering while the research engine works.

Poll `research_status` until complete. Use the `query` parameter as fallback matching -- task IDs can change between `research_start` and `research_status` calls.

### Step 5: Import Discovered Sources

Use `research_import` to bring discovered sources into the notebook for deeper analysis.

### Step 6: Query for Insights

Use `notebook_query` to ask 3-5 targeted questions based on the research type:

1. **Overview**: "What are the key findings about [topic]?"
2. **Opportunities**: "What opportunities or gaps exist in this space?"
3. **Actions**: "What are the most actionable insights from this research?"
4. **Risks**: "What are the main risks, challenges, or counterarguments?"
5. **Custom**: A question specific to the research type (e.g., "Who are the top 5 competitors and how do they differentiate?" for competitive intel)

### Step 7: Write Research Brief

Save the findings to a local file using the research brief template:

**File path:** `research/[topic-slug]-[YYYY-MM-DD].md`

Use the template from [research-brief-template.md](research-brief-template.md) to structure the output. Create the `research/` directory if it does not exist.

### Step 8: Present Takeaways

After saving, present the user with:
- **3-5 headline findings** (bullets, direct, no filler)
- **1-2 recommended actions** connected to the user's stated goals
- **Surprises or contrarian findings** -- anything that challenges assumptions
- **The file path** where the full brief is saved
- **The NotebookLM notebook URL** so the user can explore sources directly

### Step 9 (Optional): Generate Studio Artifacts

Ask the user: "Want me to generate any artifacts from this research? Options: slides, audio (podcast), video, infographic, report, mind map."

If yes, use `studio_create` with the notebook_id from Step 2.

**Available artifact types and recommended settings:**

| Type | Key params | Best for |
|------|-----------|----------|
| `slide_deck` | `slide_format`: `detailed_deck` or `presenter_slides`; `slide_length`: `short` or `default` | Executive presentations, client pitches |
| `audio` | `audio_format`: `deep_dive`, `brief`, `critique`, or `debate`; `audio_length`: `short`, `default`, `long` | Podcast-style deep dives, learning on the go |
| `video` | `video_format`: `explainer`, `brief`, `cinematic`; `visual_style`: `auto_select`, `classic`, `whiteboard`, etc. | Visual explainers, social media content |
| `infographic` | `orientation`: `landscape`, `portrait`, `square`; `infographic_style`: `professional`, `bento_grid`, etc. | One-pagers, social sharing |
| `report` | `report_format`: `Briefing Doc`, `Study Guide`, `Blog Post`, `Create Your Own` | Written deliverables, summaries |
| `mind_map` | `title` | Visual knowledge mapping |

**Common params for all artifact types:**
- `language`: Set to the user's preferred language (e.g., `"en"`, `"es"`, `"pt"`)
- `focus_prompt`: A clear directive about what to emphasize in the artifact
- `confirm`: Must be `true` to proceed with generation

**After creating an artifact:**
1. Poll `studio_status` until `completed` (audio/video: 5-15 min; slides/infographics: 2-5 min)
2. Use `download_artifact` to save locally if needed
3. Provide the notebook URL so the user can access artifacts directly

**Tips:**
- `audio` with `deep_dive` format produces the best podcast-style analysis
- `slide_deck` with `detailed_deck` format works best for standalone reading; `presenter_slides` is better when accompanied by speaker notes
- Audio status may show `"unknown"` once completed -- check for `audio_url` presence instead of waiting for a `"completed"` status

## Notes

- Fast mode is recommended as the default.
agent-evaluationSkill

Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent.

agent-expertSubagent

Use this agent when creating specialized Claude Code agents for the claude-code-templates components system. Specializes in agent design, prompt engineering, domain expertise modeling, and agent best practices. Examples: <example>Context: User wants to create a new specialized agent. user: 'I need to create an agent that specializes in React performance optimization' assistant: 'I'll use the agent-expert agent to create a comprehensive React performance agent with proper domain expertise and practical examples' <commentary>Since the user needs to create a specialized agent, use the agent-expert agent for proper agent structure and implementation.</commentary></example> <example>Context: User needs help with agent prompt design. user: 'How do I create an agent that can handle both frontend and backend security?' assistant: 'Let me use the agent-expert agent to design a full-stack security agent with proper domain boundaries and expertise areas' <commentary>The user needs agent development help, so use the agent-expert agent.</commentary></example>

agent-managementSkill

Create, manage, and orchestrate AI agents using the AI Maestro CLI. Use when the user asks to "create agent", "list agents", "delete agent", "hibernate agent", "wake agent", "install plugin", "show agent", "restart agent", or any agent lifecycle management task.

agent-manager-skillSkill

Manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.

agent-memory-mcpSkill

A hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).

agent-memory-systemsSkill

Memory is the cornerstone of intelligent agents. Without it, every interaction starts from zero. This skill covers the architecture of agent memory: short-term (context window), long-term (vector stores), and the cognitive architectures that organize them. Key insight: Memory isn't just storage - it's retrieval. A million stored facts mean nothing if you can't find the right one. Chunking, embedding, and retrieval strategies determine whether your agent remembers or forgets. The field is fragm

agent-messagingSkill

Send and receive cryptographically signed messages between AI agents using the Agent Messaging Protocol (AMP). Use when the user asks to "send a message to an agent", "check agent inbox", "message another agent", "reply to a message", "notify an agent", or any inter-agent communication task.

agent-tool-builderSkill

Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling. JSON Schema best practices, description writing that actually helps the LLM, validation, and the emerging MCP standard that's becoming the lingua franca for AI tools. Key insight: Tool descriptions are more important than tool implementa