Verified against Gemini in Gmail · 2026-06-05
Walk into a meeting already briefed, using only what's actually in your Workspace
A prompt that chains Gemini's @-mentions across Gmail and Drive to assemble a meeting brief grounded in real threads and files, instead of generic prep questions that could apply to any meeting.
The prompt
Ready to copy — highlighted parts are example details you can swap.
I have a meeting about the Q4 vendor contract renewal with the vendor's account manager and my VP of Ops coming up on this Thursday. Pull in and read through: @Gmail the thread with the vendor about "renewal terms" from the last two months @Drive the "Vendor Contract Draft v3" doc and the pricing comparison sheet Build a one-page brief: 1. Where things left off — the last concrete decision, question, or commitment from the most recent thread/doc, with its date. 2. Anything promised to the vendor's account manager and my VP of Ops that hasn't been delivered yet, or vice versa, based only on what's in the threads/docs above. 3. Open questions that are still unanswered across everything you read — don't invent a resolution if you didn't find one. 4. 4 sharp questions I should ask in this meeting, each one tied to a specific gap you found above, not a generic meeting question. If you can't find enough in the sources above to answer part of this, say which part is missing rather than filling it with a plausible guess.
Customize the highlighted detailsoptional — the prompt above already works
Why this works
Chaining @Gmail and @Drive mentions in one prompt grounds the brief in content you actually have — the real thread history and the real draft document — rather than the model falling back on generic meeting-prep boilerplate like 'ask about timeline and budget,' which it will produce confidently even with zero relevant context. The instruction to name what's missing rather than fill a gap with a plausible guess addresses a specific risk of workspace-grounded assistants: partial retrieval (a thread that didn't fully load, a doc it couldn't open) can look identical to complete retrieval in the output unless the model is told to distinguish 'I found nothing on this' from 'here's what I found.' Tying each prep question to a specific gap, rather than asking for prep questions in the abstract, is what keeps the output from being four questions any prep-for-a-meeting prompt would produce regardless of the actual situation.
Verified against
Gemini in Gmail Gemini 3 Pro · 2026-06-05
Changelog
- 2026-06-05 — Initial publish, verified against Gemini in Gmail on Gemini 3 Pro, chained with a Drive file reference.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
