agent sidequestsIdeas worth trying
An ongoing helper

Get the meeting brief before the meeting sneaks up on you

Pull the relevant history from your notes and prepare a brief before an external meeting. For customer calls, add an authorized product-usage snapshot and learn from the follow-up. Keep private notes separate from anything you share.

You get: An event-specific private meeting brief and an optional approved calendar attachmentOriginal prompt · Not run-tested

Your copy-and-paste prompt

Read as Markdown

Replace the [brackets] with your details, then paste this into your assistant.

Prepare a brief before each eligible external meeting in [calendar] using [authorized notes archive and selected email history]. Eligible means [specific event list, customer meetings, or my approved organization/domain rule]. Exclude [private events and other exclusions]. Prepare it [30 minutes] before the start in [timezone], for at most [three meetings per day]. Ask about ambiguous eligibility instead of researching every attendee on my calendar.

For the first sample, choose [event]. Confirm its date, timezone, organizer, current attendees and stated purpose. Retrieve only notes relevant to this meeting or relationship, with their dates and references. Separate confirmed decisions, open questions and commitments from my impressions. Preserve disagreement and uncertainty; an old note is historical context, not necessarily a current fact.

If requested, research up to [three] attendees using official company biographies or other public professional sources. Match the person using the company and meeting context, cite the source and date checked, and mark an uncertain identity as unresolved. Keep the background relevant to the meeting. Do not infer sensitive traits, private circumstances or hidden intentions.

For a customer or founder session, optionally add [authorized read-only product-usage export or scoped source] for [exact account ID] over [date range]. Confirm the account match, metric definitions, collection window and data freshness. Use only the selected account and fields; exclude individual-level data unless explicitly needed and authorized. Summarize the observed workflow, adoption signals and changes relevant to the meeting. Missing telemetry is unknown, not zero usage; do not infer why someone acted a certain way. Separate observed facts from at most three questions or recommendations, with the source behind each and what would confirm or contradict it. Do not expose another customer’s data, change credits, plans or permissions, or modify the product account.

Create a private one-page brief: why we are meeting; who is attending; relevant prior interactions; what was agreed and remains open; three useful questions; the decision or next step I hope to reach; and source links. Distinguish supplied facts from suggested talking points. Note inaccessible archives or incomplete research. Produce the brief in [approved private location] even when calendar attachment is unavailable.

Before attaching anything to an event, show the exact event, proposed file, current guest audience, file permissions and whether the calendar update would notify anyone. Get explicit approval for that sharing action. A calendar attachment can expose the brief to others: prepare a separate guest-safe version when needed, and leave internal notes or sensitive relationship history in the private version. Never broaden a file's permissions to make the attachment work without approval. Verify the actual event attachment and intended access after the authorized write; a saved private file alone is not an attached brief.

Maintain a ledger keyed by event ID and occurrence, with current start time, source versions, brief location and any attachment record. Update the existing brief when a meeting moves; do not create duplicate attachments. Stop preparation for canceled events. Recheck the guest list and sharing scope before later attachment updates; an earlier approval does not cover a newly expanded audience.

After the call, use only [notes I provide or authorize] to record which questions were useful, what was corrected, and which next steps I actually accepted. Propose a small update to this account’s context and to the reusable preparation checklist. Keep account-specific facts separate from general preparation preferences, retain source dates, and show a correction before applying it to future briefs. Do not automatically follow people on social media or send follow-ups; return optional drafts for my review.

For recurring preparation, confirm access, lead time, scheduling or event-trigger support, and verify the saved setup. If unavailable, give me a manual prepare-this-meeting prompt. Do not alter event times, invite people, email attendees or publish notes.
What the result could look like

Illustrative: the useful history, kept with its source

An illustrative private brief could surface a question left open in the last customer conversation, link the relevant note and suggest three questions for today. A separate version omits internal commentary before you decide whether to share it with the event’s guests.

Illustrative example. This is not an observed result or a verified recommendation.
The real-world spark

Inspired by a reported use

Describes preparing founder sessions from public background, connected product usage and call notes, then using call feedback in later preparation.

Shub Gaur on Founder Bot · Grok Bot Builder Demos

Vendor-affiliated presenter at Grok Bot Builder Demos; the public transcript was read, but the workflow was not independently reproduced. The presenter identifies the displayed material as demo data. Real customer telemetry, recommendations and time savings were not independently verified. Our optional account-usage and feedback additions are untested extensions. The prompt above is our original extension, not the author's exact prompt or a tested result.

Make it more you

For an account review, combine a read-only usage snapshot with prior call notes, then carry confirmed corrections into the next brief. For a first meeting, stay with the agenda and verified professional background when internal data is unavailable.

Get more from this idea

Keep the ideas coming

All sidequests
An ongoing helper

Wake up to a 6am brief that remembers yesterday

Combine your calendar, email and meeting notes into a short morning PDF. Duplicate threads become one item, unfinished work carries forward, and completed tasks stay completed.

You get: A dated morning PDF and a persistent action register with completion historyGet the promptCommunity-inspired idea