rtk-ai/rtk

Add rewrite rules for notebooklm CLI (source/artifact/generate/create/use/list)

Open

#1231 opened on Apr 11, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
effort-mediumenhancementgood first issue

Description

Context

rtk discover flagged notebooklm as the #1 unhandled command in my Claude Code usage — 37 invocations across 30 days, more than any other command without an RTK equivalent. Sharing the data in case it's useful for prioritization.

Breakdown (from rtk discover)

Subcommand Count Example
`notebooklm source` 13 `notebooklm source add /path/to/file`
`notebooklm artifact` 13 `notebooklm artifact list --json`
`notebooklm generate` 5 `notebooklm generate slide-deck "..."`
`notebooklm create` 2 `notebooklm create "Notebook title"`
`notebooklm use` 2 `notebooklm use "Notebook name"`
`notebooklm list` 1 `notebooklm list`
`notebooklm notebook` 1 `notebooklm notebook info -n ""`

What `notebooklm` is

Community CLI for Google NotebookLM exposing notebook CRUD, source management, and artifact generation/retrieval. Several subcommands emit verbose JSON or long source listings — good rewrite candidates for `--json` trimming or output summarization, similar to how `rtk npm` and `rtk git` work today.

Suggested prioritization

  • Highest savings likely: `artifact list`, `source list`, `notebook info` — JSON-heavy, verbose output.
  • Lower priority: `generate`, `create`, `use` — small output, rewrite probably not worth the maintenance cost.
  • Rules would live in `src/discover/registry.rs` following the existing pattern.

Happy to contribute a PR if the direction is agreed — just flagging the usage data first.

Contributor guide

Tech stack
rust
Domain
cli
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic Rust knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Start by examining the existing rewrite rules in src/discover/registry.rs, especially the npm and git rules. Understand the struct and method for defining rewrites. Then implement rules for the most impactful subcommands (artifact list, source list, notebook info) as suggested in the issue. Consider using the provided usage data to prioritize. Note that the issue author is open to contributing a PR, so coordinate if needed.