notebooklm-vault

Sync Obsidian vault content with Google NotebookLM for persistent project memory.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/HelloWorldSungin/ark-skills --skill notebooklm-vault
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notebooklm-vault
Source: https://github.com/HelloWorldSungin/ark-skills/tree/main/skills/notebooklm-vault
Command: npx skills add https://github.com/HelloWorldSungin/ark-skills --skill notebooklm-vault

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires notebooklm-py, jq, and includes scripts (resource) components.

What problem does it solve?

Persistent memory and context for Ark projects by syncing the Obsidian vault with Google NotebookLM, enabling you to recall decisions, session history, and research efficiently across sessions.

Core Features & Use Cases

  • Bridges the Obsidian vault with NotebookLM to provide a centralized, searchable memory store for project knowledge.
  • Maintains session logs, architectural decisions, research notes, and strategy documents to support warm starts, audits, and reports.
  • Use cases include answering questions about past sessions, resuming work, and generating vault-based summaries or reports.

Quick Start

Run the notebooklm-vault setup to bootstrap the vault and establish the NotebookLM link for persistent project memory.

Frequently Asked Questions about notebooklm-vault

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync my Obsidian vault with Google NotebookLM for persistent project memory?

You can sync your Obsidian vault with NotebookLM using a skill that relies on per-project config at .notebooklm/config.json and supports incremental and full sync workflows to maintain persistent project memory.

Does notebooklm-py support incremental sync workflows for per-notebook routing?

Yes, notebooklm-py is used to support incremental and full sync workflows with per-notebook routing, relying on vault state tracked at vault/.notebooklm/sync-state.json to manage the synchronization process.

What is the best way to recall past architectural decisions and session history across projects?

Integrating your Obsidian vault with NotebookLM maintains session logs, architectural decisions, and research notes as a centralized memory store, enabling you to recall past decisions and resume work efficiently across sessions.

Can I generate reports from Obsidian vault content using NotebookLM?

You can generate vault-based summaries and reports by integrating your Obsidian vault with NotebookLM, which enables you to answer questions about past sessions and compile strategy documents directly from your stored vault content.

Do I need jq to bootstrap NotebookLM vault integration for warm starts?

Yes, jq is required alongside notebooklm-py to bootstrap the vault and establish the NotebookLM link, providing the persistent project memory needed to support warm starts and resume previous work sessions.

When should I use a full sync workflow instead of an incremental sync for my vault?

You should use a full sync workflow when establishing your initial vault state or resolving context gaps, whereas incremental sync efficiently updates per-notebook routing for routine session history and research notes.