notebooklm

Name: notebooklm
Availability: InStock
Author: ydemir

Save and query project decisions and deployment notes in NotebookLM.

Updated Feb 28, 2026

Search Tags:#memory #notebooklm #project-management #session-context #decision-logging #deployment-tracking #repomix-sync

Ready to run

npx skills add https://github.com/ydemir/openclawmaster --skill notebooklm-ydemir

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: notebooklm
Source: https://github.com/ydemir/openclawmaster/tree/main/.claude/skills/notebooklm
Command: npx skills add https://github.com/ydemir/openclawmaster --skill notebooklm-ydemir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Save and query project memory in NotebookLM to persist decisions, design docs, and deployment notes across sessions and workflows. This skill acts as the long-term memory layer for OpenClawMaster and triggers automatically at session start, task completion, error resolution, and after repomix sync.

Core Features & Use Cases

Save decisions and design docs to NotebookLM for easy retrieval in future sessions.
Query project history and deployment notes to reconstruct context, rationale, and open decisions.
Automatic memory capture at session start, task completion, error resolution, and after repomix sync to keep context up to date.

Quick Start

Log a decision or deployment context to NotebookLM so it remains accessible for future sessions.

Frequently Asked Questions about notebooklm

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

FAQPage Schema

How do I persist project decisions and deployment notes across sessions?▼

You can query project history in NotebookLM by retrieving past deployment notes and design docs. This reconstructs historical context, rationale, and open decisions, ensuring you maintain continuous project awareness across different sessions.

How do I log decisions and design docs for future retrieval?▼

You log decisions and design docs by allowing the skill to automatically capture context at session start, task completion, error resolution, and after repomix sync. This ensures all deployment notes and historical context are saved to NotebookLM for future retrieval.

Can I use repomix sync to update project memory automatically?▼

Yes, you can use repomix sync to update project memory automatically. The skill triggers memory capture after repomix sync to log decisions, deployments, and historical context, keeping your NotebookLM project history continuously synchronized.

Do I need the notebook memory MCP to query deployment tracking?▼

Yes, you need the notebook memory MCP to query deployment tracking. The skill interacts directly with the notebook memory MCP, using the notebook ID from docs/notebooklm-notebook-id.txt, to read and write project session context.