---
name: gnkg
description: "Use the user's Gemini Notebook notebooks as knowledge graphs through the GNKG bridge (MCP tools gn_* and bifrost_*). Trigger on: notebook, Gemini Notebook, NotebookLM, knowledge graph, GNKG, B.I.F.R.O.S.T., bins, push a folder into a notebook, ask my notebook, generate an audio overview / slide deck / report / mind map from a notebook, or /gnkg."
---

# /gnkg — drive Gemini Notebook as a knowledge graph

1. **Health first.** Call `gn_health`. If `extension` is false or `auth` is not "ok", stop and tell the user: open Chrome with the GNKG extension loaded and sign in at notebooklm.google.com, then retry. Do not ask for credentials.
2. **Locate.** `gn_list_notebooks`; match the notebook the user means by title. Create one with `gn_create_notebook` only when asked.
3. **Map before you ask.** `gn_get_notebook` and `gn_graph` show sources, bins, artifacts and their status. Use them to choose `sourceIds` for a scoped `gn_ask`.
4. **Add knowledge.** Small text → `gn_add_text_source`; a URL → `gn_add_url_source`; a folder or codebase → read the files, then `bifrost_push_bins` (project slug + optional `directive` that steers later Studio artifacts). Poll `gn_job` until `status: done`; report the pushed bin → source map.
5. **Ask.** `gn_ask` returns Gemini Notebook's grounded answer. Quote it, cite which notebook and sources, and do not embellish beyond it.
6. **Generate.** `gn_create_artifact` with the requested `kind` and the user's focus as `instructions`; `wait: true` for ≤ 15 min jobs, otherwise poll `gn_wait_artifact`. Offer `gn_download_artifact` when completed.
7. **Receipts.** End with what was created (ids, titles, statuses) and what is still pending. A `jobId` or `pending` artifact is not done.

Never delete sources/artifacts without explicit confirmation. If tools error with drift/shape messages, use `gn_dom_read` for read-only fallback and say so. The MCP server is `npx -y @metaphyllc/gnkg-bridge` (stdio) or `http://127.0.0.1:7802/mcp`.