meeting-brief

/kola:meeting-brief

Pulls Kola's full memory on one person into a single, scannable prep memo.

Instructions

1. Resolve the person. Pick the best Kola tool for the input:

   • Plain name → search_people (substring on display_name).
   • Email → query_people with WHERE email1 = ? OR email2 = ? OR email3 = ? OR email4 = ? over v_people_full.
   • LinkedIn URL or Telegram handle → query_people against linkedin_url / telegram_handle.
   • Multiple matches → list the top 5 by recency (COALESCE(updated_at, created_at) DESC) and ask the user which one.
   • Zero matches → say so and stop. Offer to capture them via /kola:save-contact.

2. Hydrate. Call get_person for the canonical row, then in parallel:

   • get_person_emails — recent Gmail history (cap to last 10 most recent).
   • get_person_telegram_messages — recent DMs (cap to last 10).
   • get_person_whatsapp_messages — recent WhatsApp (cap to last 10).
   • get_person_linkedin_messages — recent LinkedIn DMs (cap to last 10).
   • list_custom_fields — for any per-install fields set on this person, format the values via the person's custom_fields object.
   • semantic_search_notes — query by the person's name (and company) to surface notes you've jotted that mention them. Dedupe against people.notes, which you already have.
   • semantic_search_recordings — query by the person's name (and company) to surface call transcripts where they came up; fetch the full text with get_recording_transcript only for the closest hit.

   Notes and recordings aren't person-scoped, so a hit is a candidate — keep only snippets that plainly reference this person, and drop the rest.

   If --depth fast, skip the message-history fetches and the notes/recordings semantic searches, and use only the counts already on get_person (email_count, telegram_dm_count, whatsapp_dm_count, calendar_event_count).

3. Render the memo in this exact order — headers omitted when their section is empty:

   # <display_name>
   <position> @ <company> · <location>
   
   ## Identity
   - Email: …
   - LinkedIn: …
   - Telegram: …
   - WhatsApp: …
   - Phone: …
   
   ## Custom fields
   <key>: <value>
   …
   
   ## Lists
   <name>, <name>
   
   ## Recent threads (last <N> across channels, newest first)
   [<date> · <channel>] <subject or first line>
     <one-line summary>
   
   ## Notes
   <freeform notes from people.notes, verbatim>
   
   ## Mentioned in (notes & calls)
   [note · <date>] <title> — <one-line gist>
   [call · <date>] <recording title> — <one-line gist of the relevant moment>
   

4. Closing line — what to ask about. From the recent thread summaries, propose 2–3 specific topics worth bringing up. These should be evidence-anchored ("you mentioned X on Y date") — not generic openers.

Examples

/kola:meeting-brief Jane Smith
/kola:meeting-brief [email protected]
/kola:meeting-brief https://www.linkedin.com/in/janesmith --depth fast

Output

A self-contained markdown memo. No external links beyond what's stored on the person row. If Kola has nothing for that person, the memo says so plainly rather than padding.