Other

/gemini-research

Deep research, compare options: Gemini Deep Research. NOT for Exa web search, drive-filing or report links.

$ golems-cli skills install gemini-research

Updated 1 week ago

Default: prepare a grounded prompt for Gemini Deep Research at gemini.google.com.

Triggers on: gemini research, Gemini Deep Research, deep research, compare research options.

Grounding default: attach files, Drive source off. Agents prepare ONE folder holding exactly the curated grounding files with unique names. The hand-off names that folder and the files to attach; the owner attaches them when he starts the run with Drive source off. Drive grounding is optional, never the default. Its connected Drive workspace supports title SEARCH only: it cannot list a folder or open a document by link. Native Google Docs do not fix this limitation.

Measured 2026-11-13/14: four runs read none of the grounding files, with both raw Markdown and converted Docs. A Deep Research probe correctly quoted one Doc's first line after title search, but found only 2 of 7 Docs. Plain Gemini chat could read the same Docs by folder, title and link; that does not establish Deep Research access. Three subsequent runs used attached files with Drive off and passed the author-held answer key (PR 1267).

Grounding prep — your FIRST action, before any search or draft

Done condition: no research prompt leaves this skill until ONE of these is true:

  • Project-grounded (the default): a /research-lifecycle preparation receipt is back, naming ONE prepared folder and exactly the curated grounding files in it, with unique names.
  • Web-only (only when the user says the question needs no project state): the prompt's # Grounding block has the exact line None — web-only research and a separate Reason: <the user's reason> line. These replace the receipt.
  1. Right after loading this skill, dispatch ONE sub-agent. Do not search Drive, grep or draft the prompt yourself first. Its brief says: "Run /research-lifecycle preparation for : verify local context, refresh the Drive grounding corpus for provenance, prepare ONE folder holding exactly the curated grounding files with unique names, and return that folder, the exact file names to attach with Drive off, and the lifecycle receipt." Pick its execution profile per /agent-routing § Execution capability (Drive write + shell); a read-only gatherer may only report staleness.
  2. Web-only branch: when the user says the question needs no project state, skip step 1, write the exact web-only line and separate reason, and go straight to the emit gate below. The grounding and START/EDIT gates still apply.
  3. Project-grounded: name the prepared folder and files to attach in the hand-off; the owner attaches them when he starts the run with Drive source off. Draft the prompt from the receipt's exact file names. While preparation runs or is blocked, tell Etan the prompt follows the receipt; never emit it before.

Include one line in the hand-off: "Prepared folder: ; files to attach: ; attach this prepared set when starting the run, with Drive source off." Preparation is the agent's job; do not emit a prompt that asks Etan to collect files.

Optional Drive route — exact titles and a probe first

If Drive is used, verify every grounding document's title is unique across the whole Drive, with no duplicate or look-alike titles. Name each document by its exact title in the prompt, never by folder or link. Expect title search to miss documents; a connected source and an author-side Drive read prove no researcher access.

Before the real run (for either source route), run one cheap Deep Research probe that asks only for each named document's first line. Compare every returned line against the author key, retaining the probe and comparison receipt outside the researcher prompt. Any missing or mismatched line blocks the real run. For Drive, switch to supplied files or correct the titles and repeat the probe; never fire the real prompt on an unverified set. The probe does not replace the real run's admission table or author-held answer key.

Curated grounding set, admission stop, provenance

  • Curated, bounded set: agents prepare ONE folder holding exactly the curated grounding files with unique names, name that folder and the files to attach in the hand-off, and keep a provenance copy. The owner attaches the prepared set when starting the run with Drive source off (/drive-filing § Research grounding folder contract). The folder organizes the record; it is not a Deep Research access route. The prompt names the exact files and says to use ONLY them.
  • Admission table with a HARD STOP: before firing, the prompt's # Grounding block carries a read-check table, one row per grounding file, with readable: yes/no. Project-grounded runs only; web-only research keeps its own None — web-only research block and has no table. Any row that is not an affirmative verified read (no, blank, missing, empty, truncated, unreadable) stops the run: output only the table and a MISSING FILES list. The template holds the wording.
  • Author-held answer key: keep exact source answers and real first headings/lines in the author record's admission-key JSON inside # Pre-fire checks, never the emitted researcher text. Cover every named document and admission question. Emit refuses missing keys or verbatim answer leaks. readable: yes alone proves nothing: on 2026-11-13 NarrationLayer R02 with six attached grounding files invented all six answers (1.05 vs 1.5; 0.179 vs 0.484); the private key caught them. Earlier Drive-grounded runs stopped honestly with readable: no rows.
  • Keep the stop in the plan: when Gemini's generated plan drops the stop, return it for EDIT and paste this sentence: If any read-check row is not an affirmative verified read (readable: no, blank, missing, empty, truncated or unreadable), output only the read-check table and a MISSING FILES list, and stop.
  • Provenance: the harvest record names the model, the settings (Drive on/off, Search on/off, mode), the prompt sha256, the grounding manifest_sha256 and the folder's link, so the run's identity survives later consolidation. Write unknown only for a field you could not read.

ROUTING — Gemini Deep Research by default

  • Research and comparisons → gemini.google.com → Deep Research. Use a structured prompt, review the generated plan, then obtain the prompt author's START / EDIT verdict.
  • Quick lookups or summaries of content already in Drive → connected Drive search tools.
  • NotebookLM on request: only for an explicit notebook, podcast/audio overview, slides or quizzes request, read the opt-in workflows.