notebooklm-routerlisted

# NotebookLM router ## Prerequisite This skill's ideal path needs a NotebookLM MCP server configured, authenticated once, and a notebook created and loaded with the project's authoritative documents (see SETUP.md). That prerequisite is not required to use the skill at all: routing itself never touches the network, and every command below runs with no account configured. When the `notebook` destination is chosen but the server or notebook is unavailable, say so plainly and fall back to a local search of the codebase or product docs instead of stalling on a source that cannot answer. ## Routing procedure 1. Run the scorer against the question: ``` uv run python scripts/route.py --question "<the question>" --config routes.example.toml --json ``` 2. Read `destination` from the output. If `reason` is `"ambiguous"`, do not guess - ask the user which source they mean, or rephrase the question with the missing signal (see `references/routing-rules.md`). 3. Follow `action` for the winning destination. For `notebook`, that means calling the NotebookLM MCP server's ask-question tool with the notebook id read from the `notebook` field (or from `${NOTEBOOKLM_NOTEBOOK}` directly) and requesting footnote-style citations. 4. Apply `references/citation-policy.md` to whatever comes back before using it: verify the citation, never accept a bare synthesis. ## Routing table | Destination | What it holds | Route here when the question... | |---|---|---| | `notebo