Cookie 静默刷新技能

Refresh and persist Google NotebookLM cookies for notebooklm-py authentication.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/crimes342/skills --skill cookie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Cookie 静默刷新技能
Source: https://github.com/crimes342/skills/tree/main/skills/notebooklm/skills/cookie-refresh
Command: npx skills add https://github.com/crimes342/skills --skill cookie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents NotebookLM authentication failures by automatically refreshing and persisting the Google cookie used by notebooklm-py, so the API remains usable without manual re-login.

Core Features & Use Cases

  • Three-layer refresh reliability: refreshes on a fixed cron schedule, refreshes on-demand when a 401 occurs, and persists login state via the CloakBrowser profile to act as a final fallback.
  • Cookie-to-API seamless data flow: pulls cookies from CloakBrowser (CDP) and bridges them into Playwright storage_state used by notebooklm-py.
  • Operational controls & verification: supports scheduled execution, an environment-variable trigger, and monitoring/validation steps (including an auth test and log inspection).

Use case: You run NotebookLM in a long-lived environment and want to avoid daily manual cookie renewal when Google sessions expire.

Quick Start

Tell your Hermes assistant to refresh cookies (for example by saying "刷新 Cookie" or "Cookie 过期了") and then confirm the result with an auth test.

Frequently Asked Questions about Cookie 静默刷新技能

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

FAQPage Schema
How do I keep NotebookLM cookies fresh without manual re-login?

To keep NotebookLM cookies fresh without manual re-login, you can use an automated silent refresh mechanism that pulls cookies from CloakBrowser and persists them into notebooklm-py storage_state.

What is the best way to automate Google session persistence for NotebookLM in a long-running environment?

Automating Google session persistence for NotebookLM involves scheduled cron execution and 401-triggered refresh commands to silently update CloakBrowser profile storage_state for notebooklm-py consumption.

How does a 401-triggered cookie refresh work with CloakBrowser and notebooklm-py?

A 401-triggered cookie refresh works by detecting authentication failures and executing a NOTEBOOKLM_REFRESH_CMD to pull fresh cookies via CDP and bridge them into Playwright storage_state.

Do I need a cron scheduler to maintain uninterrupted access to the NotebookLM API?

You do not strictly need a cron scheduler because a 401-triggered refresh and CloakBrowser profile persistence act as fallback layers, but scheduled bridge execution provides the highest refresh reliability.

Why does my notebooklm-py authentication fail during long-running Hermes sessions?

NotebookLM-py authentication fails during long-running Hermes sessions because Google cookies expire, requiring silent refresh mechanisms to pull new cookies from CloakBrowser and update the storage_state.

Can I trigger a NotebookLM cookie refresh using an environment variable?

You can trigger a NotebookLM cookie refresh using the NOTEBOOKLM_REFRESH_CMD environment variable, which pulls cookies from CloakBrowser and updates the storage_state for notebooklm-py.