AGENT SKILL

wowerpoint

Turn one document into a kawaii NotebookLM slide deck. Use for "wowerpoint this", "make a deck about <file>", "turn this report into slides", or any request to render a single document as shareable narrative slides.

License 许可
Apache-2.0
最近更新
2026-10-19
Stars
★ 0
Forks
0

01 前言 Front Matter

name
wowerpoint
description
Turn one document into a kawaii NotebookLM slide deck. Use for "wowerpoint this", "make a deck about <file>", "turn this report into slides", or any request to render a single document as shareable narrative slides.

03 SKILL.md 正文

Wowerpoint

One doc in, one deck out. Slide-deck only — videos and podcasts from the same engine are noticeably worse and out of scope; refer the user to the notebooklm CLI directly if they want those.

Triggers

  • "Wowerpoint <file>"
  • "Make a slide deck about <file>"
  • "Turn this report into slides"
  • "Kawaii-deck this"

Setup (one-time per machine)

If notebooklm auth check returns 0 and command -v jq resolves, skip.

uv tool install --with playwright --force notebooklm-py
$(uv tool dir)/notebooklm-py/bin/playwright install chromium

jq is required by the workflow's JSON parsing; install if missing (brew install jq on macOS, or your distro's package manager).

Then the user authenticates interactively — do not script. Tell them to type ! notebooklm login so the OAuth ENTER lands in their terminal.

Workflow

1. The source doc

You need exactly one source doc. If it doesn't exist or is too thin to carry a deck, write it first — use mem-search and sequential thinking to make it comprehensive (long-form, narrative, several thousand words is normal). Do not paper over a weak source by adding more sources.

2. Auth pre-flight

notebooklm auth check 2>&1 | tail -5

Exit 1 with Run 'notebooklm login' to authenticate. = halt and tell the user.

3. Create notebook, add the source

NOTEBOOK_ID=$(notebooklm create "<title>" --json | jq -r .notebook.id)
notebooklm source add "<doc-path>" --notebook "$NOTEBOOK_ID" --json

Title: H1 of the source doc, or its filename stem; append a date for dated work.

create returns the id at .notebook.id; a wrong key gives an empty string and a silent downstream failure.

4. Generate the deck

notebooklm generate slide-deck "<PROMPT>" --format detailed --length default --notebook "$NOTEBOOK_ID" --json --retry 2

5. End your turn

Print the notebook URL:

https://notebooklm.google.com/notebook/<NOTEBOOK_ID>

NotebookLM sends the user a notification when the deck is ready.

The prompt

One sentence. Default:

Use kawaii characters to tell the story of <subject>. Keep it warm and clear.

Replace <subject> with a one-phrase description from the source doc's H1 or the user's framing. If the user supplies their own prompt, pass it through verbatim — don't expand it.

Failure modes

  • pip: command not found — modern macOS doesn't ship pip on PATH. Use uv tool install.
  • Playwright not installed — install notebooklm-py with --with playwright, then playwright install chromium.
  • Run 'notebooklm login' to authenticate — only the user can complete OAuth.
  • Rate-limit (GENERATION_FAILED or "No result found for RPC ID") — --retry 2 handles transients; persistent failure means wait 5–10 minutes or fall back to the web UI.
  • Source upload denied for sensitive docs — confirm before adding sources containing credentials, customer data, or unreleased product info. NotebookLM is a Google service.
  • --length long does not exist — only default|short. If the user asks for "long slides," use default and explain.
  • No --style flag — kawaii lives in the prompt text.

Operational tips

  • Rerun cheaply — once the notebook + source exist, regenerating with a different prompt only repeats generation. Reuse NOTEBOOK_ID.
  • Web UI fallback — if generation is rate-limited >30 minutes, open the notebook URL and trigger generation in the UI.

04 同仓库更多 Skills

Prasanth595
Prasanth595/claude-mem

what-the

What the? Use when the user wants a plain-English breakdown of something technical — the who, what, where, why, and when.

★ 0
Prasanth595
Prasanth595/claude-mem

weekly-digests

Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests", "week-by-week story", "serial timeline", or "narrative chapters" of a project's history.

★ 0
Prasanth595
Prasanth595/claude-mem

version-bump

Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. Ends with the agent running npm publish itself using the maintainer's npm token.

★ 0
Prasanth595
Prasanth595/claude-mem

timeline-report

Generate a "Journey Into [Project]" narrative report analyzing a project's entire development history from claude-mem's timeline. Use when asked for a timeline report, project history analysis, development journey, or full project report.

★ 0
Prasanth595
Prasanth595/claude-mem

standup

Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.

★ 0
Prasanth595
Prasanth595/claude-mem

smart-explore

Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.

★ 0