{"call_it":"\"Brief me before external meetings\" by James Raybould","owner":"James Raybould","runbook":"https://myrunbook.ai/jamesraybould","n":6,"id":"prep","name":"Brief me before external meetings","runner":"an assistant I built","schedule":"twice a day","description":"A one-page brief in my assistant app for each external meeting I flag, with where we left it, who owes what and what they've posted lately.","reads":["calendar events","email and text history","meeting notes","LinkedIn and web research"],"lands":"A one-page brief in my assistant app","loop":"Meeting notes and open promises feed the next brief about the same person","source":null,"figure":"19 briefs written in the last 30 days","link":null,"example":{"kind":"invented","note":"Thu 15 Oct, 14:00. Priya, operations lead at Fenwick Labs. Third conversation.\nWhere you left it: she wanted a smaller first phase. You said you would think about it.\nYou owe: a view on the revised scope.\nWhat they have posted: hiring a data lead last week.\nUnconfirmed: may be moving offices (a colleague said so)."},"output":"Meeting brief","build":"Ask first\n- Which meetings get a brief? (default only ones you flag)\n- Which sources may it read? (default calendar, mail, messages, notes; web search for new people)\n- Who counts as known well? (default 10 or more exchanges in the last year)\n- How long? (default about 700 words for a first meeting, 250 for someone known well)\n- Where should it land? (default a page in your assistant; optionally one email to you per meeting)\n- How far ahead does the refresh look? (default the next 36 hours)\n\nNeeds\n- Calendar events with attendee names or addresses; else the person names the attendee when flagging.\n- Mail and message history with the attendee; notes if kept. Thin history is fine: the brief says so and leans on public sources.\n- Web search; optionally a logged-in browser for recent posts, else skip posts.\n- A store for briefs keyed by event, with a notes box the person fills in.\n- Connecting mail and messages: \"It reads only threads with the people you flag; it never writes to them.\"\n- If your assistant can only chat: say \"prep me for X on Thursday\" and paste the last thread; steps 3 to 5 work on what you paste.\n\nBuild\n1. Read (trigger): the person flags a meeting or names someone. Pin down who from something verifiable (employer, city, a shared thread). Two candidates fit: ask, never guess.\n2. Read (sync): pull messages first, so a text from an hour ago is in.\n3. Read (gather): the oldest thread with them (why the meeting exists), recent texts, the web, their latest posts, anything pasted.\n4. Decide (familiarity): count exchanges in the last year. Known well means 10 or more: no biography; cover what changed, what they have done for the person, what they still owe. Under 10: a short biography first.\n5. Decide (write): bullets, each a bold claim with the evidence under it. \"Done\" and \"Owed\" as separate lists. Promises quoted word for word. Anything unverified in \"Unconfirmed\" with what would settle it. No talking points or suggested questions.\n6. Deliver: store the brief against the event and show it; if email is on, email the person once, when first built, and a stored sent flag stops a second email. Fallback: one message. Each run refreshes briefs for flagged meetings in the next 36 hours.\n7. Memory: the brief, its sent flag, and the notes box, which feeds the next brief on the same person. 2 to 5 model calls per brief.\n\nCheck\n- Flag a past meeting and run with delivery off: a brief with a \"Where you left it\" block from a real thread, every claim traceable to a source you read.\n- A meeting with no flag: nothing is written.\n- Quiet run: a sweep with no flagged meetings logs one line; the first real run shows as a stamp on the brief page.\n\nIn my version\n- Q, my assistant, on my Mac, twice a day, reading Google Calendar, Gmail, iMessage, WhatsApp, meeting notes and web search. LinkedIn and X posts come from captures I run with my /prep skill in a logged-in browser. Briefs on Q's prep page; the email copy is switched off.","built":{"method":"POST","url":"https://myrunbook.ai/api/runbooks/_bSFet4kFzjy/built","body":{"job":"prep","by_handle":"<your own runbook handle, if you have one>","note":"<what you built, what you changed, what broke; up to 1200 characters>"},"ask_first":"Only send this after the person says yes.","link_for_the_person":"https://myrunbook.ai/jamesraybould/built?routine=6"}}